An incoming invoice also called a purchase invoice or supplier invoice is a billing document received from a supplier requesting payment for goods or services delivered. Unlike a sales invoice you issue yourself, an incoming invoice lands in your accounts payable queue and triggers an obligation to pay. For businesses operating at scale, managing incoming invoices accurately is critical: missed due dates mean late-payment penalties, incorrect VAT recording creates compliance risk, and manual data entry introduces errors that are expensive to trace. Understanding what an incoming invoice contains and how to process it systematically is the foundation of healthy payables management.
What is an Incoming Invoice
An incoming invoice is a formal request for payment sent by a supplier after fulfilling an order or contract. It typically includes the supplier’s name, VAT ID, and country code; the customer’s corresponding identifiers; a unique invoice number; invoice date and due date; line items with amounts excluding VAT; the VAT amount; and the total amount including VAT. The currency is also stated, which matters for cross-border transactions.
Modern incoming invoices arrive in several formats: structured XML (such as UBL or EDIFACT used in Peppol networks), PDF attachments, scanned paper images (PNG, JPG), or embedded in email bodies. Each format requires a different parsing approach, though the underlying data fields are standardised. The invoice type (standard invoice, credit note, debit note) and a type code further classify the document and determine how it should be posted in your accounting system.
Incoming Invoice vs Purchase Order
A purchase order (PO) is a document your organisation sends to a supplier to authorise a purchase. The incoming invoice is the supplier’s response confirming the sale and requesting payment. The two documents should match: the goods, quantities, prices, and VAT treatment on the invoice should correspond to what was ordered.
This matching process often called three-way matching when a goods receipt is also included is the primary control against being overbilled or paying for goods never received. When an invoice arrives without a corresponding PO, or when amounts diverge, the invoice should be held for manual review before payment is authorised. In practice, many small businesses skip formal POs for recurring suppliers, accepting invoices on trust, which increases the risk of errors going undetected.
Processing Steps
Incoming invoice processing follows a predictable lifecycle. First, the invoice is received and registered the system notes the registration date, assigns a source (Peppol, email, manual upload), and sets the initial invoice status. Second, the document is parsed to extract key fields: invoice number, supplier VAT ID, customer VAT ID, amounts, dates, and currency. Third, the invoice is validated mandatory fields are checked, VAT amounts are verified, and the supplier is matched against your records.
Fourth, the invoice moves to approval if your workflow requires it. An approver reviews the line items, confirms the amounts, and may add comments before authorising payment. Fifth, payment is recorded: the amount paid, the payment date, and the remaining balance are tracked. Finally, the invoice is archived with its full history status changes, comments, and payment events for audit purposes.
Common Processing Errors
Several errors repeatedly appear in accounts payable operations. Duplicate invoices occur when the same invoice is submitted twice once via email and once via Peppol, for example and are caught only if the system checks for duplicate invoice numbers per supplier. Missing VAT IDs prevent correct tax posting and may invalidate input VAT recovery. Incorrect due dates, often caused by misreading European date formats, lead to premature or late payment. Currency mismatches arise when a EUR invoice is posted against a PLN payable.
Amount discrepancies between the stated amount excluding VAT and the line-item sum indicate either a supplier error or a parsing failure. Invoice status stalling where an invoice sits in “Processing” without progressing points to a parsing problem that requires manual intervention. Each of these errors is easier to catch early, before payment is released, than to reverse after the fact.
How Docnova Manages Incoming Invoices
Docnova’s incoming invoice module centralises receipt, tracking, and payment recording in one place. Invoices arrive via Peppol network, email inbox, or manual upload (XML, PDF, PNG, JPG); after upload, documents show a “Processing” status while Docnova parses the content. The main list view displays all key fields SOURCE, INVOICE TYPE, INVOICE NUMBER, SUPPLIER NAME/TITLE, SUPPLIER VAT ID, CUSTOMER VAT ID, INVOICE STATUS, PAYMENT STATUS, AMOUNT EXCL. VAT, AMOUNT INCL. VAT, CURRENCY, REGISTRATION DATE, INVOICE DATE, and DUE DATE with filter controls for date range, invoice type, status, payment status, and source.
Opening any invoice row slides in a detail drawer that shows the financial breakdown (amounts excl. VAT, VAT, incl. VAT, paid, remaining) alongside a payment status combobox. The “Enter Payment” action lets you record a manual payment directly against the invoice, updating the paid and remaining amounts in real time. A Comments tab supports internal discussion threads, and a History tab provides a full audit log of every status change. Bulk selection and a totals footer summarising excl. VAT, incl. VAT, and outstanding amounts round out the workflow.
Conclusion
Incoming invoices are the entry point for your accounts payable cycle. Processing them systematically receiving, parsing, validating, approving, paying, and archiving reduces errors, protects VAT recovery rights, and keeps supplier relationships healthy. The more of that cycle you can automate and centralise, the fewer exceptions fall through the cracks.