Accounts payable in Microsoft Dynamics 365 Business Central works the way most mid-market ERP AP modules work: it handles the transaction layer well. Purchase invoices can be created, matched to purchase orders, approved, and posted. Payment runs can be generated and executed. Vendor ledger entries are maintained accurately. The ERP does what ERPs are designed to do. What Business Central does not do is manage the document that triggers all of that activity: the vendor invoice that arrives as a PDF in someone’s email inbox before any of the ERP workflow can begin.
The gap between the moment a vendor invoice arrives and the moment it becomes a Business Central transaction is where most AP teams lose the most time, introduce the most errors, and create the most compliance exposure. Paperwise Symphony closes that gap by automating every step between invoice receipt and ERP posting, creating an end-to-end AP process where the only human intervention required is exception handling and approval decisions.
What the Manual Gap Actually Costs a Business Central AP Team
To understand what Symphony automates, it helps to map the manual steps that currently exist between invoice receipt and BC posting for a typical Business Central AP environment:
An invoice arrives as a PDF attachment to the AP inbox. A staff member opens the email, downloads the attachment, and opens it to read the relevant fields. They navigate to Business Central and create a new purchase invoice record. They key the vendor name, invoice number, invoice date, due date, and amount from the PDF into the BC fields. They attach the PDF to the BC record. They navigate to the purchase order module to find the corresponding PO and manually enter the PO number into the invoice record. They check the line items against the PO to confirm the match. If the invoice matches, they route it for approval by emailing the appropriate approver with the invoice attached. The approver reviews the email, opens BC to check the PO, replies to approve, and the AP staff member returns to BC to post the invoice.
Every step in that process except the final posting is manual document handling. An experienced AP staff member can complete this workflow in 10 to 15 minutes for a clean, matched invoice. For an invoice with discrepancies, the process takes longer and may involve additional email exchanges before posting. At 200 invoices per month, the labor cost of that manual workflow is significant and the error rate is meaningful.
What Symphony Does to the Same Workflow
Symphony transforms that workflow by automating every manual step and removing human involvement from everything except exception resolution and approval decisions:
When a vendor invoice arrives in the monitored AP email inbox, Symphony captures the attachment automatically without requiring any human interaction. The intelligent capture engine reads the invoice, identifies it as a vendor invoice, and extracts the vendor name, invoice number, invoice date, due date, line items, quantities, unit prices, and total. Those extracted fields are validated against the vendor master in Business Central to confirm the vendor exists and that the extracted vendor name matches the BC vendor record.
Symphony then queries Business Central for open purchase orders that could match the invoice, using the extracted vendor identifier and invoice amount to identify candidates. When a matching PO is found, Symphony performs the three-way match automatically: comparing the invoice quantities and prices against the PO quantities and prices, and checking the receiving record to confirm that the goods or services were received.
Invoices that pass the three-way match automatically are routed through the configured approval workflow in Symphony, with notifications sent to the appropriate approver based on the vendor, cost center, or invoice amount. Approvers review the invoice in Symphony with the matching PO and receiving record displayed alongside it, and approve with a single action. The approved invoice is then posted to Business Central automatically, with the PDF attached to the BC transaction record and all extracted fields populated without manual entry.
The entire process from email receipt to BC posting happens without a human touching the invoice unless the match fails or the approval is required.
Handling Exceptions Without Losing Efficiency
Not every invoice matches cleanly. A vendor invoices at a price that differs from the PO. A quantity discrepancy exists between the invoice and the receiving record. A vendor number extracted from the invoice does not match any active vendor in BC. These exceptions require human judgment, and Symphony’s exception handling workflow surfaces them efficiently without creating the same bottleneck that manual processing creates for every invoice:
- Price discrepancy exceptions are routed to the purchasing team with the specific line item discrepancy identified, so the reviewer can confirm whether the price difference reflects an authorized change or an invoicing error
- Quantity discrepancy exceptions are routed to the receiving team with the receiving record alongside the invoice, making the discrepancy immediately visible without a separate research step
- Vendor identification exceptions queue the invoice for AP review with the extracted vendor information displayed, allowing quick manual matching to the correct BC vendor record
- Invoices without a matching PO are routed to the appropriate cost center owner for coding and approval through a configurable non-PO invoice workflow
The key difference from manual processing is that Symphony routes each exception to the correct person with the specific issue identified, rather than requiring AP staff to identify the issue, locate the relevant comparison documents, and determine who should resolve it.
Connecting the Document Archive to the BC Transaction Record
One of the most operationally significant capabilities of the Symphony and Business Central integration is the automatic attachment of the original invoice PDF to the BC transaction record at the point of posting. When an auditor, a vendor, or a finance manager needs to see the original invoice for a posted transaction, they find it directly attached to the BC record without requesting it from AP.
This connection creates several downstream benefits that extend well beyond the initial processing efficiency:
- Vendor inquiries about payment status can be resolved by finance staff directly from BC without involving AP to locate and forward the original invoice
- Internal audits of the AP function can be completed from BC transaction records without requesting original documentation from AP
- Period-end close processes that require invoice review are completed faster when original documents are accessible directly from the transaction record
- Dispute resolution with vendors who claim non-receipt of payment can be resolved with both the payment record and the original invoice accessible in the same system
Three-Way Matching at Scale
The three-way matching capability that Symphony automates is the most labor-intensive and error-prone step in most Business Central AP workflows. At low invoice volumes, manual matching is manageable. At high volumes, it becomes a bottleneck that limits how quickly invoices can be processed and increases the error rate as staff work under time pressure.
Symphony’s automated three-way matching operates at any volume without degrading in accuracy or speed:
- Matching logic is applied consistently to every invoice regardless of volume peaks or staff availability
- Match results are documented automatically, creating an audit trail of the matching decision that manual processes cannot replicate
- The exception rate, the percentage of invoices that require human review for matching discrepancies, is typically 10 to 20 percent of total invoice volume in a well-configured deployment, focusing human attention on the transactions that actually require judgment rather than the routine matches that can be automated
Implementation Without Disruption
The most common concern about adding automation to an established Business Central AP process is implementation disruption. Symphony is designed to minimize that disruption by connecting to Business Central through standard APIs without requiring modifications to the BC environment. The existing BC configuration, including vendor master, purchase order workflow, and posting rules, remains unchanged. Symphony operates as a layer in front of BC that handles document management, and the BC experience for finance staff who work with posted transactions and financial reporting is unchanged.
Contact the Paperwise team to discuss what a Symphony implementation looks like for your specific Business Central environment and where the most significant AP automation gains are available in your current invoice processing workflow.
