PeakGP Invoice · available now
From invoice PDF to Dynamics GP, ready for a click.
PeakGP Invoice reads vendor invoices with AI, finds the vendor, matches the purchase order, codes the lines, and creates the right document in Dynamics GP. Your AP team confirms instead of retypes.
How it works
Four steps, and the last one is yours.
- Drop it inUpload PDFs on the page, or drop them in a watched folder. A mail rule can feed that folder from your AP mailbox.
- It reads itAI extracts the vendor, number, dates, lines, tax, freight, PO number, and whether it is an invoice or a credit memo. The vendor is matched from its tax ID, name or past choices.
- It checks itTotals, accounts, duplicates and the purchase order are checked against your GP, and GP itself is asked to build the document in a test run that is rolled back. Clean ones are marked Ready.
- You confirmReview what needs attention, then upload the ready ones in one click. GP gets the transaction, with the original PDF attached.
What it creates
The right GP document for each invoice.
The page always says which one an invoice will become, and the checks and the test run apply to that same document.
Non-PO invoice
A Payables invoice in an unposted batch, coded to your GL accounts. Lines are pre-filled from how that vendor was coded before, and from the same wording on its earlier invoices.
Tax goes under the GP tax detail; freight goes to the account you choose, or onto the first line.
PO invoice
An invoice entered through Receivings, matched to the purchase order lines. Goods that were received are matched to their receipts. Drop-ship, blanket and lump-sum lines are billed in as many phases as the vendor sends.
You see the PO's own lines, what has been billed, and what is left. A vendor invoice number already on the PO is caught.
Credit memo
A Payables credit memo with the same amounts on the opposite side of the ledger. Credit notes printed with negative amounts are handled, and PO matching is not applied to them.
Built for the person doing the work
The review screen is where the time is saved.
- The PDF beside the form, with a summary strip of supplier, number, dates and totals, and a banner that says exactly what GP will create.
- Pre-filled from memory. For each vendor it remembers the GL account, tax detail, currency and freight handling, and which PO line a given wording was billed to.
- The ready queue. A background check keeps every invoice's status current, including after each edit. Tick the ready ones, or select them all, and upload.
- Keyboard first. Save, validate, upload and jump to the next invoice without the mouse.
- An assistant that only reads. Ask what the last invoice for this vendor was, which GL accounts it used, or what is still open on a PO. It answers from GP and cannot change anything.
- Intake folder. PDFs dropped in a share are picked up, uploaded and filed away as processed, duplicate or failed, with the reason for any failure.
- Sign-in for each person. Users and administrators are managed in the app, with lockout after repeated wrong passwords.
- Attachments. The original PDF is attached to the GP document, so anyone in GP can open it.
Controls
Nothing is created that the checks or GP would reject.
Validated
Lines, tax and freight must add up to the invoice total. Vendors, GL accounts and tax details must be active in GP. The invoice number is checked against GP and against earlier uploads.
Proven before upload
GP is asked to build the actual document in a test run that is rolled back. If GP would refuse it, the invoice is not marked ready and the reason is shown.
Auditable
Who uploaded, saved and posted each invoice is recorded. Invoices go into unposted GP batches, so your existing review and posting steps still apply.
Fits your environment
It runs where your GP runs.
PeakGP Invoice is installed on your own Windows server and talks to your own SQL Server. An installer walks through the settings and tests access before it changes anything, and updates are a single package.
Invoice PDFs are sent to Anthropic's Claude API to be read. See the privacy page for what is sent and what is not.
| Dynamics GP | Built and tested against Dynamics GP 2018. Other versions on request. |
|---|---|
| Server | Windows Server with IIS and the .NET 8 hosting bundle |
| Database | SQL Server access to your GP company, plus a small staging database the installer creates |
| AI service | An Anthropic API key and outbound HTTPS to api.anthropic.com; usage is billed by Anthropic |
| Companies | One GP company per installation |
Where it stops today
- On a PO invoice, a price that differs from the PO or receipt price is refused with an explanation rather than posted, because price variances are not posted by this tool yet.
- Foreign-currency PO invoices are not supported yet; those are entered in GP, or as Non-PO invoices.
- Invoices arrive by upload or watched folder. Reading a mailbox directly is not built yet.
- "Ready" means the checks and a GP test run passed. It does not mean the AI read every field correctly, which is why a person still decides.
See it on your own invoices.
Send us a handful of typical vendor invoices, including a PO invoice and a credit note, and we will show you what it does with them.