Question
Closed · Answered

How would you have Buda check invoice totals after extracting the data?

Hovhannes Vktarget

I'd like to put a batch of supplier invoice PDFs in Drive and have Buda extract invoice numbers, amounts, and tax into a table.

What matters most to me is the checking afterward. If the line items don't match the total, an amount is unclear, or the currency is missing, I'd want that invoice flagged for review.

Would you have it check the arithmetic with a script before producing the summary? If this becomes a Skill, which validation rules would you define upfront?

Report
Kelly
Team
· edited

Add a check gate after extract: line items vs total, currency present, amounts readable. Failures go to a review list; the summary only includes passes.

(Diagram: PDF batch → extract → check script → summary vs review.)

(Local demo: finance / invoice scenario session)

Suggested steps

  1. Batch PDFs in Drive, one invoice per row/record, keep originals.
  2. Extract number, amounts, tax, lines, currency into a table.
  3. Script the checks (best inside a Skill)
  • Sum of lines vs invoice total (small tolerance, e.g. 0.01);
  • Missing currency, unclear amount, missing pages → review;
  • Split pass vs review lists/statuses.
  1. Summarize passes only; clear the review list before bookkeeping/payment.

How to confirm

  • Break a line total on purpose → it must land in review, not the summary.
  • Review rows state why (math / currency / unclear).
  • Original PDF still opens from the same record.

Boundaries

  • Extracted ≠ bookable without a check status.
  • OCR errs; scripts catch arithmetic/missing fields — still spot-check critical invoices.
  • Multi-currency batches summarize per currency, never raw-sum mixed currencies.
Report

Your reply

Sign in to join the discussion. Reading is always open; you only need an account to post.

Sign in