Skip to content
allanninal.dev/build
Collaborate

Part 6 of 7 · Invoice dispute triager series ~5 min read

What the invoice dispute triager costs

Dispute volume is low even in businesses that feel overwhelmed by them — fifteen a month is a normal figure for a firm raising four hundred invoices. The bill reflects that: this is one of the cheapest systems in the series to run, and the value is entirely in the hours it gives back rather than in anything it costs. Here is where each cent goes.

Key takeaways

  • About $2 a month at 40 disputes. Roughly $3 at 150 disputes.
  • One Bedrock read per dispute is the only line that scales. Everything else is rounding.
  • Nothing is always-on, so a quiet month genuinely costs almost nothing.
  • The duplicate test runs before the read, so resends are free.
  • The three real risks: a retry loop, storage nobody expires, and a bigger model than the job needs.

The bill at three volumes

These are US East prices at the time of writing, at three volumes that bracket most small businesses. Find the bar closest to your own and read across.

Monthly cost of the invoice dispute triager at three volumesA stacked bar chart with three bars, one per volume tier: 10 disputes totalling about $1, 40 disputes totalling about $2, and 150 disputes totalling about $3. Each bar is stacked from bands. The largest and fastest-growing is Bedrock, one read per dispute, in teal. Then SES for the messages, in pink. Then S3 and DynamoDB storage in green. Then a fixed orange band for Secrets Manager and AWS Budgets, which is eighty-six cents at every volume. Then a grey band for Lambda, SQS and CloudWatch. A note says the read is the only bar that grows with the business and the orange band never moves.$0$1$2$3$4~$1.3310 disputes~$1.640 disputes~$2.58150 disputesBedrock — one read per disputeSES — asks, results, receiptsS3 + DynamoDBFixed — Secrets Manager, BudgetsLambda, SQS, CloudWatchThe read is the only bar that grows with the business. The orange fixed band never moves.
Fig 1. The monthly bill at three volumes. The teal band — one model read per dispute — is the only part that grows; the orange fixed band is the same 86 cents at every volume.

Line by line

LineAt 40 disputesHow it scales
Bedrock read$0.29Linear. One call per dispute, roughly 1,800 in and 200 out tokens.
SES$0.03Linear. About 2.2 messages per dispute.
DynamoDB + S3$0.29Storage grows with what you retain, not with throughput.
Lambda + SQS$0.12Linear, and effectively free at this scale.
CloudWatch$0.16Flat, if you set retention. Unbounded if you do not.
Secrets Manager$0.40Flat. One secret, $0.40 a month.
AWS Budgets$0.46Flat. Two actions, so you find out before the bill does.

The read cost per dispute is higher than in most systems here because the prompt carries the invoice lines as well as the customer message. That is the right trade: it is what lets the classifier identify which line is being disputed, which is what makes the gathering narrow.

The three ways this bill surprises you

Every one of these has happened to somebody, and all three are cheap to prevent.

  • Classifying every inbox message. If the cheap structural filters are skipped and every message that arrives gets a model call, a single customer’s out-of-office loop can cost more in a week than a year of real disputes. Auto-reply and remittance detection are free and must come first.
  • A retry loop on a malformed attachment. A dispute email carrying a corrupted PDF makes the function throw, and without a dead-letter queue the queue redelivers indefinitely. Maximum receive count of three.
  • Log retention left at never. At this volume the logs will out-cost everything else within months. Thirty days of retention is the whole fix.

What it costs when nothing happens

This matters more than the headline number for a seasonal business. In a month with nothing to process the bill is the fixed band: Secrets Manager at forty cents, AWS Budgets at forty-six, and a few cents of storage. Call it a dollar. There is no instance to stop and nothing to remember to turn off.

The monthly bill at four volumes plus one failure modeA horizontal row of five boxes. Quiet month, about one dollar. 10 disputes, about $1. 40 disputes, about $2. 150 disputes, about $3. And one bad retry loop, about two hundred dollars. A note says four of these are the design working and the fifth is a missing dead-letter queue.THE BILL, AT A GLANCEQuiet month~$110 disputes~$140 disputes~$2150 disputes~$3One bad loop~$200Four of these are the design working. The fifth is a missing dead-letter queue.
Fig 2. The bill at a glance, including the one that is not a volume at all. A retry loop with no dead-letter queue costs more than every legitimate use of the system put together.
  • Management
  • Analytics
  • Front-end & mobile

Set these on day one

  • A dead-letter queue on every SQS queue, with a maximum receive count of three.
  • Thirty-day retention on every CloudWatch log group. There is no default that is safe.
  • An S3 lifecycle rule on the object prefix, tiering at 90 days and expiring at your actual record-keeping horizon.
  • Two AWS Budgets actions — one that emails at half your expected spend, one at double it. The second is how you find out about a loop in an hour instead of a month.
  • Provisioned concurrency: none. Nothing here is latency-sensitive enough to justify paying for a warm function.

Next: the same system drawn for engineers — service names, resource identifiers, IAM scopes, table schemas and the model id.

All posts