What we do
Tools
Industries
Department
How we workLet's talk →
Home/Acumatica/Acumatica AP Automation for Non-PDF Bills
Acumatica

Acumatica AP Automation Reads Your PDF Bills. These Are the Ones It Can't.

The recognition mailbox is live, PDFs turn into bills on hold, and approval maps send each one to the right manager. Then the freight carrier sends its weekly charges as a CSV, a supplier in Toronto dates invoices day-first, and a bill against a purchase order arrives with no receipt number on it. Acumatica's AP automation is real and native. The work left sits in the bills that don't fit how it reads.

How a bill reaches Acumatica, and what's left for AP

The bill arrives as What Acumatica does with it Left for the AP team
A PDF emailed to the recognition mailbox A system email account submits each PDF attachment to Incoming Documents. AP Document Recognition reads it, and once someone reviews it, Save and Continue creates the bill on hold with the PDF attached. Vendors not yet in Acumatica and unfamiliar layouts come back partly filled. Files over 10 MB aren't accepted.
A PDF someone drags in or files from Outlook Incoming Documents takes single uploads or a batch, and the Outlook add-in creates the document straight from an attachment. Someone still has to spot the email and do it.
A bill against a purchase order Recognized purchase order and receipt numbers are copied onto the bill's lines. When billing is by receipt and no receipt number is printed, the lines get linked to the receipt by hand.
A CSV, XML or EDI file from a large supplier Recognition reads PDFs only. The bill gets keyed, or someone runs an import scenario for each file.
An invoice posted on the vendor's own portal Nothing native fetches it. Someone logs in and downloads it, unless the portal can email invoices or offers an API.

Bills that reach Acumatica in a shape recognition skips

A freight carrier's weekly CSV, a supplier's EDI 810 or an XML e-invoice never reaches recognition. For those, n-frames builds an intake that reads the file, finds the vendor and lines in Acumatica, and creates the bill through Acumatica's REST API, on hold and with the original file attached. It then waits for the same approval map as every other bill.

Approvers who check something Acumatica doesn't hold get a check that runs before they open the bill. n-frames builds the step that compares the bill with the outside budget, contract rate or receiving log, and writes the result onto the bill where the API allows, so the approver sees it next to the amount.

Licensing and approval questions for Acumatica AP

Acumatica is set up through partners. The answers decide how many bills stay manual.

  • How many recognized documents does our license cover?

    AP Document Recognition has to be enabled, and the number of documents it reads is capped by the license. A heavy month can run past it.

  • Will vendors email a dedicated mailbox, or will staff forward bills to it?

    Acumatica advises a mailbox used only for AP bills. Forwarding a general AP inbox pulls statements and payment reminders into Incoming Documents too.

  • Which approval maps apply to bills, and on what conditions?

    Bills from recognition are created on hold, and approval maps route them by the conditions you set. Agree who signs at which amount before go-live, not after the first disputed payment.

  • Where does the information an approver checks actually live?

    If the approver looks at a project budget, a contract rate or a receiving log kept outside Acumatica, approval maps can't see it. That check is a build, not a setting.

  • How will approved bills get paid?

    Acumatica prints checks and creates batch payments for electronic transfers, and payment partners extend the methods. Decide the route before vendors start asking for remittance details.

Let's talk

Every bill on hold in Acumatica, whatever format it came in

Acumatica reads the PDFs and runs the approvals. n-frames builds the intake for CSV, EDI and XML bills, plus the pre-approval checks against data Acumatica doesn't hold, all on Acumatica's REST API.

Budget checks before approval →

Acumatica AP automation, the built-in parts and the rest

Does Acumatica have AP automation built in?

Yes. AP Document Recognition reads PDF bills from a mailbox or an upload and fills in the vendor, lines and any purchase order and receipt numbers. Bills are created on hold, approval maps route them, and payments run from Acumatica. Recognition has to be enabled and included in your license.

Does Acumatica use AI to read bills?

Its AP Document Recognition sends each PDF to a recognition service that reads the fields, and someone reviews and corrects the values before the bill is saved. Acumatica keeps adding AI features, so ask your partner what your version includes.

Can Acumatica pull bills from a vendor portal automatically?

Not natively. Its intake is a mailbox, an upload or the Outlook add-in. Where the portal can email invoices, point it at the recognition mailbox. Where it has an API, n-frames builds the step that fetches each invoice and delivers it there. A portal with neither still means a manual download.

Does Acumatica handle AP payment processing?

Yes. It prints checks and builds batch payments for electronic transfers from approved bills, and payment partners add other methods. The payment closes the bill in the same system.

Why does recognition get the dates wrong on some supplier bills?

Acumatica's documentation says files should use the US locale, with month-first dates. A Canadian or UK supplier's 03/04 can come through as March 4 instead of April 3, so check those bills before saving or route those vendors through a different intake.

Let's talk

Tell us the one thing your team does manually that eats up time. We read every message and reply within a day.