Organize Receipts and Bookkeeping

Turn scattered financial evidence into a traceable register and a clean review handoff.

Prepare the records for the accepted:

• owner;
• finance team;
• bookkeeper;
• accountant;
• reviewer.

Do not decide accounting treatment or change financial records.

1. Define the handoff

Establish:

• company/entity;
• period;
• currencies;
• approved sources;
• destination;
• reviewer;
• definition of complete.

Learn existing:

• register fields;
• naming rules;
• matching rules;
• filing conventions;
• review format.

Possible approved sources include:

• email;
• vendor portals;
• billing tools;
• payment records;
• files;
• existing spreadsheets;
• accounting exports.

Use visible logged-in browser sources when that is where the evidence lives.

Suggest new connections only when they materially improve the selected outcome.

2. Gather only in-scope evidence

Retrieve only documents and records inside the accepted period and entity scope.

Preserve where available:

• source link;
• document date;
• vendor/payee;
• amount;
• currency;
• transaction reference;
• retrieval date;
• original filename.

Store or rename files only in the accepted destination and naming convention.

Keep original evidence available.

Do not let the spreadsheet row become the only surviving record.

3. Build or update the register

Create a reviewable register containing the accepted fields.

Keep each entry traceable to the underlying document or transaction evidence.

Do not alter source records to make the register cleaner.

4. Match conservatively

Match a receipt or invoice to a payment only when the evidence supports the relationship.

Consider:

• identifier;
• amount;
• currency;
• date;
• counterparty;
• context.

Do not force a match from amount alone.

Classify items as:

• supported match;
• missing invoice;
• missing receipt;
• ambiguous match;
• partial match;
• possible duplicate;
• unexpected vendor;
• unexpected payer;
• unexpected amount;
• unexpected date;
• requires accounting/tax judgment.

5. Calibrate new matching rules

When:

• source is new;
• matching rules are new;
• volume is large;

show a small varied sample first.

Apply accepted corrections before processing the rest.

Do not scale an uncertain matching method automatically.

6. Validate the collection

Where possible, reconcile:

• register count;
• totals;
• source coverage.

Check:

• duplicates;
• currency consistency;
• date consistency;
• links;
• filenames;
• exception visibility.

Do not claim the books are reconciled when only supporting evidence has been organized.

7. Deliver the handoff

Provide:

• organized evidence;
• register;
• exception list;
• short handoff note.

The note should cover:

• scope;
• source coverage;
• unresolved items;
• questions for reviewer.

When the next task is understanding what changed financially, route to financial-performance review.

8. Preserve the accepted bookkeeping-prep method

After the user accepts:

• fields;
• sources;
• matching rules;
• filing convention;

preserve them for future collections.

A recurring workflow may:

• retrieve documents from named sources;
• prepare the register;
• surface exceptions.

It should stop when:

• entity changes;
• account changes;
• period changes;
• source changes;
• destination changes;
• matching confidence falls outside accepted limits.

9. Maintain strict action boundaries

Reading financial records does not authorize transactions.

Do not:

• initiate payments;
• approve payments;
• schedule payments;
• alter payments;
• post entries;
• reverse entries;
• categorize entries;
• approve accounting entries;
• change bank records;
• change ledger records;
• change payroll;
• change invoices;
• change source records;
• share financial information beyond the accepted audience.

Stop for review when:

• MFA is required;
• new account access is needed;
• identity changes;
• entity changes;
• sensitive data scope expands.