Upload a PDF, a photo or a scan. Stamparoo reads the document, suggests your
GL code, office and project code, then stamps them onto the PDF as real,
editable form fields — and keeps a running ledger and vendor directory as it goes.
Reads anything you throw at it
Text PDFs, photos from your phone, and scanned pages with no text layer at
all — those are read visually instead.
Your chart of accounts
Suggestions come from your own GL codes, offices and project codes, each with
a stated reason and confidence rather than a bare guess.
Locked, approval-ready coding
Coding is baked cleanly into the saved PDF as a locked record — no messy
editable-field boxes, and no silent changes after approval. Corrections
happen in the app, with a trail.
Learns your vendors
It remembers how you actually coded each vendor last time — including your
corrections — and uses that as a starting point next time.
A product by Workgroup (WA) Pty Ltd
No access
You don't have access to this workspace.
A product by Workgroup (WA) Pty Ltd
Log in
New here?
Create your workspace
.stamparoo.app
Already have a workspace?
Been given a join code?
Join a workspace
Already joined?
A product by Workgroup (WA) Pty Ltd
Send feedback
Stamparoo
Stamp it. Submit it. It's Sorted.
—
—
Workspace—
Address—
1 AI reading
Upload a PDF first.
2 Invoice
▤
100%
Page 1 of 1
CODED · STAMPAROO
REF—
GL—
OFC—
PRJ—
APPR—
DATE—
ABN—
GST—
Need a separate code marked at a specific spot — e.g. a different cost centre for one line item? Place an individual stamp:
Tip: right‑click a stamp, or drag it off the page, to delete it. On GL stamps, the ⟲ icon re-checks that code by looking specifically at the page around it.
Highlight anything on the document yourself — click and drag over the area you want marked:
Tip: right‑click a highlight to erase just that one.
Turn this off if you only want individual field stamps below, with no red coding block.
Defaults to page 1. Individual field stamps can already go on any page — this is specifically for the main coding block.
Tip: drag the red stamp directly on the invoice to fine-tune its position.
3 Coding block
AI thinks this might be a — that's not in your document types list.
4 Coding ledger — saved on this device
No invoices coded yet. Once you save a stamped PDF, it'll be logged here.
5 Vendor directory — unique vendors, built up automatically as you code invoices
No vendors captured yet. Coding your first invoice will create its first entry here.
R Documents for review — sent here manually when a separate person approves
Nothing awaiting review.
6 Settings — adjust the coding taxonomy and defaults used across Stamparoo
General
Where new invoices arrive. The two destinations below are where a source file is moved once you've dealt with it — leave either blank to use a subfolder of the watch folder.
The intake log stamparoo-intake-log.csv is written in the Processed folder.
Coding taxonomy
The lists Stamparoo suggests from and validates against everywhere — the Coding form, AI suggestions, and every stamp.
Adding a whole chart of accounts? Use Backup & restore configuration at the bottom of Settings to import them from a CSV in one go.
Populates the Document type dropdown on the coding form. "Invoice" and "Credit Note" have specific built-in behaviour (green and red stamp colour respectively; "Statement" additionally gets the diagonal watermark and a relabelled date field) — renaming or removing them turns that behaviour off for whatever no longer matches. Anything else, including Receipt and Remittance, gets the blue stamp used for all other document types.
Each tier applies up to its amount; the last tier is the catch‑all for anything above.
Integrations
ABN verification is now managed centrally by your platform operator — the "Verify" button next to a vendor's ABN works automatically, with no GUID to configure here.
Being upfront: a one-click "Connect to Xero" login isn't achievable from a browser-only tool like this one. Xero's OAuth API needs a backend server to securely handle app credentials, and Xero's own developer docs state single-page apps aren't a supported client type for their no-secret (PKCE) flow. Two ways to still pull your codes in below — Option A works for everyone.
In Xero: Accounting → Advanced → Chart of accounts → Export for GL codes. Needs at least a Code column and a Name column, comma-separated.
If you already hold a valid Xero OAuth access token and tenant ID (e.g. pulled via Xero's API Explorer or Postman), Stamparoo can try calling the API directly from your browser. This will very likely fail — Xero's API isn't designed to be called straight from a browser — but it's harmless to try, and falls back cleanly to Option A if blocked.
Email notifications
⚠ You're viewing this inside an embedded preview (like Claude.ai's artifact panel) right now. Browsers block embedded pages from opening mailto: links or the share sheet as a security measure — so email testing will silently do nothing here, even though the same code works normally once deployed. Download the file and open it in a real browser tab, or host it, to actually test this feature.
Being upfront about what this can and can't do: there's no mail server behind a static page like this, so Stamparoo can't send email on its own. When you save with the checkbox ticked, it tries your browser's native share sheet first (Web Share API) — where supported, this hands the actual stamped PDF to whatever email app you pick, genuinely attached. Where that's not supported (notably Firefox, and older/desktop Safari), it falls back to opening a pre-filled email draft in your default mail app instead — but a plain email link can never attach a file automatically on any browser, so in that fallback case you'll need to attach the just-downloaded PDF yourself before hitting send.
Only the share sheet (mostly mobile) and the .eml file can actually attach the PDF for you — a plain mailto link cannot, on any browser. On desktop the .eml route is the one that arrives with the invoice attached; just double-click the downloaded .eml and hit Send.
Variables you can use in the subject or body — each gets replaced with that invoice's actual value when you save: $VENDOR $DOC_TYPE $INVOICE_NUMBER $INVOICE_DATE $DUE_DATE $AMOUNT $GL_CODE $OFFICE $PROJECT_CODE $APPROVER $VENDOR_ABN $NOTES $FILENAME
Backup & restore configuration
Everything you've configured above lives only in this browser — it won't follow you to another device or survive clearing browser data. Download it as CSV to back it up, hand it to a colleague, or move it to a fresh install.
Captures every Settings value in one file — taxonomy, approval tiers, theme, default stamp position, panel widths, the lot. Download it here and upload it into any other Stamparoo instance (a different browser, device, or deployment) to make that instance match this one exactly.
Team & access
Workspace members
Coding changes awaiting your approval
A team member coded a vendor differently from the established value. Approving replaces it for everyone; rejecting keeps the current value and stops it being asked again.
Decisions on your proposed coding
Version —
Where this prototype stops short of production: it codes one page at a time and stores the ledger, vendor directory, and settings locally in this browser rather than in a shared database; a real deployment would need line‑item level coding for multi‑item invoices, OCR for scanned (image‑only) PDFs, an actual chart‑of‑accounts feed from your ERP (NetSuite/SAP/Xero/QuickBooks), role‑based approval routing with real notifications, an audit trail of who edited what and when, and ABN validation against the real ABN Lookup registry rather than trusting what's printed on the invoice. Vendor de‑duplication here is a simple name/ABN match — a production system would want a review queue for uncertain merges.
