Tally API
Reconciles purchase order paperwork against Fulfil so finance can land POs with confidence. Tally finds the purchase order a document refers to, compares supplier invoices and packing lists against the order and what was received, and posts any variance to Slack.
Tally never lands a purchase order. Landing in Fulfil can't be undone, so it stays a human step.
What it doesβ
| Area | What happens |
|---|---|
| PO lookup | Resolves a vendor reference (for example FS065) or a PO number to its Fulfil purchase order, and lists orders received but not yet invoiced |
| Documents | Labels documents by type, matches them to a PO, and reads the totals and PO references out of PDFs and spreadsheets |
| Tie-out | Compares a document's totals and per-SKU lines against the purchase order or the received shipment |
| Alerts | Posts supplier invoice, shipment and needs-review alerts to Slack |
Who calls itβ
Only n8n, from the Finance Ops workflows. n8n moves the files between Gmail, Google Drive and Sheets; Tally holds the Fulfil access and the reconciliation rules. See n8n Workflows.
How it's reachedβ
| Environment | Base URL |
|---|---|
| Production | https://api.birdygrey.com/tally |
| Staging | https://api.birdystaging.com/tally |
Every request goes through the Birdy Grey API Gateway and needs an API key in the x-api-key header. The service can't be called directly.
API referenceβ
- Interactive docs: api.birdygrey.com/tally/public/docs
- OpenAPI spec: api.birdygrey.com/tally/public/openapi