MetadevXInnovate. Code. Create.MetadevXInnovate. Code. Create.

(01) The challenge

The ERP was fine; typing into it was not

Purchase orders, invoices and customs paperwork arrived as PDFs and email attachments, and a team of eleven re-keyed them into the ERP by hand. Every error was found downstream, usually at payment, and every correction cost more than the original entry.

  • · 4,300 documents a month re-keyed by hand
  • · 2.4% correction rate, caught mostly at payment run
  • · Month-end close took nine working days

(02) Approach

Extract, validate, and keep a human on the exception

We built a pipeline that reads each document, extracts the fields the ERP needs, validates them against vendor master data, and posts only what passes. Anything ambiguous lands in a review queue with the source page highlighted, so a human decides in seconds instead of retyping minutes.

  • · Document AI extraction across five vendor templates
  • · n8n orchestration with Python validation services
  • · Exception queue with audit log on every automated post

(03) Outcome

70% of manual entry eliminated, close down to four days

Straight-through processing now covers seven of every ten documents. The team moved from data entry to exception review, and month-end close went from nine working days to four without adding headcount.

70%

Manual entry removed

0

Day-one posting errors

4 days

Month-end close

(04) What we did

We automated the boring half first

Before touching the model we mapped every document type and its failure history. That map decided the order of work: highest volume, lowest ambiguity first, so the team banked time savings while the harder templates were still being tuned.

  • · Process map with volume and error history per document type
  • · Template-by-template rollout with a review queue fallback
  • · Post-ERP integration with PostgreSQL ledger and n8n flows
  • · Governance pack: who approves, what is logged, how to roll back
Next projectCloud Observability & FinOps Suite→