Match
Exactly one PDFEach eligible row must resolve to one invoice file. Zero or multiple matches stop safely instead of guessing.
PDF invoice delivery / test-data pilot
Turn billing rows and a Google Drive invoice folder into a bounded delivery pilot with exact file matching, safe stops, test delivery, outcome logging, duplicate protection, and controlled resend.
Do not pay until the pilot boundary is approved in writing. The pilot uses redacted or synthetic data and does not send to live customers. Stripe payments are processed by AIMart.trade; your statement will show AIMART.TRADE.
01 / What the pilot proves
Match
Exactly one PDFEach eligible row must resolve to one invoice file. Zero or multiple matches stop safely instead of guessing.
Deliver
Controlled test sendValid pilot rows are sent only to one buyer-approved test recipient, never to the live customer list.
Record
Outcome and replay controlSent, skipped, and failed outcomes are logged with enough state to block accidental duplicates and permit an explicit resend.
02 / Fixed boundary
The fixed price excludes invoice generation, accounting or tax decisions, OCR, production credentials, customer data, new subscription costs, live activation, and unrelated workflow changes. Any production rollout receives a separate written scope after the pilot is accepted.
03 / Acceptance evidence
Positive
Valid row, one PDFOne test message is produced with the expected attachment and the row receives its delivery record.
Negative
Missing, duplicate, or invalidMissing PDF, multiple matches, bad email, or incomplete data stops before delivery and records a useful reason.
Replay
Duplicate block and controlled resendAn already-sent row cannot fire again accidentally; a deliberate resend follows an explicit operator-controlled path.
04 / Before paying
It covers up to five redacted sample rows, billing-cycle selection, exact Google Drive PDF matching, delivery to one buyer-approved test recipient, sent and error logging, duplicate-send protection, controlled resend behavior, test evidence, and a short runbook.
No. The pilot uses redacted or synthetic rows and one buyer-controlled test recipient. Live customer delivery and bulk activation require separate written approval after the pilot passes.
The workflow should stop that row safely, record the reason, and send nothing. A row proceeds only when its required data is valid and exactly one PDF matches.
The target is three business days after payment, the written boundary, and complete safe test inputs are confirmed. Missing or unsafe inputs pause the delivery clock.
No. One Workflow Fixed is an independent service and is not affiliated with, endorsed by, or sponsored by Google or Make.
Start with the boundary
Send redacted structure, not credentials or customer records.