A little knowledge. A clearer next step.

Build confidence in the details behind your records. Learn why an invoice differs from a settlement, how an opening balance supports a review and what makes an AI-assisted draft worth trusting.

Launch access Contact us

Choose the task in front of you

Start with the question you need to answer. Follow a guide through the source records, the checks and the handoff. Keep a note of what is known and what still needs another person’s judgment, so progress does not depend on remembering every detail.

Use examples as a way to reason

The worked examples use fictional records to explain a process. Replace them with your own checked source data before making a business decision. If a question concerns tax treatment, legal duties or a regulated activity, bring the relevant evidence to the professional responsible for it.

01Keep the source02Check the context03Choose the next step

Keep a good thought going

Explore this section.

Find a topic

Check the customer name before sending.

A familiar contact name may not be the business that should appear on the invoice. Resolve the difference while the document is still a draft.

Describe the work someone can recognize.

A line description should help the recipient connect a charge to work they agreed to buy.

Keep quantities and units together.

A number is easier to check when the reader knows whether it describes hours, sessions, items or a package.

Separate the service period from the document date.

The work may cover a different period from the day its invoice is prepared.

Carry the purchase-order reference through.

A missing customer reference can slow review even when the amount and description are correct.

Check line arithmetic independently.

A tidy total can hide an incorrect quantity or rate. Recalculate the lines before reviewing the whole document.

Make an agreed discount visible.

The recipient should be able to understand how an agreed adjustment affects the displayed amount.

Check the source of the due date.

A due date should follow the agreed terms rather than the default in an old template.

Put the currency beside the amount.

A dollar sign alone can leave an international recipient unsure which currency a draft uses.

Give the final draft a fresh review.

The last check should cover the actual version being released, not an earlier draft that happened to be correct.

Make the invoice understandable.

A clear invoice lets someone recognize the work, check the amount and ask a precise question. These guides cover the details that are easy to overlook when preparing a draft.

Keep evidence of what was sent.

A file in a folder does not by itself show which document the customer received.

Show a partial payment without losing the original amount.

A payment can reduce an open amount without replacing the invoice it relates to.

Turn a customer query into a precise review item.

A message saying “this looks wrong” needs context before someone can resolve it.

Keep the correction trail readable.

Someone reviewing a corrected document should be able to understand what changed and why.

Investigate a payment without an invoice reference.

A received amount is a starting point for a match, not proof that the nearest-looking invoice is settled.

Explain one payment covering several invoices.

One bank amount may settle more than one document, so retain the allocation behind the total.

Recognize a duplicate sending event.

Sending the same invoice again does not create a second sale or a new document amount.

Make the open-items list useful.

An open item should tell the next person what is missing, not merely that something is unfinished.

Review a customer statement against its sources.

A summary is useful only when each line can be traced to the invoice, payment or adjustment behind it.

Close a follow-up with a reason.

A completed status should explain what was resolved so the next person does not have to reconstruct the conversation.

Follow the record, not your memory.

Invoices, replies, partial payments and corrections create a trail. Keep that trail understandable so a follow-up refers to the right document and the right open question.

Explain the purpose while it is fresh.

A merchant name often tells the reviewer less than the person who made the purchase remembers.

Check a possible duplicate before removing it.

Similar dates and amounts can identify a question, but they cannot prove that two records describe one purchase.

Make a missing receipt an explicit task.

A bank description can show activity without explaining exactly what was purchased.

Keep a mixed-purpose purchase understandable.

One receipt may contain items that need different review decisions.

Distinguish a reimbursement request from its receipt.

The request explains who seeks repayment; the receipt explains the purchase.

Investigate an unfamiliar merchant description.

A statement label may differ from the familiar name on a receipt.

Keep purchase and posting dates distinct.

The day a purchase happened may differ from the day it appears on a statement.

Review a recurring charge against its context.

A familiar monthly amount still deserves a connection to the underlying service.

Link a refund to the original purchase.

A refund needs enough context to show which event it reverses or adjusts.

Make the expense queue answerable.

A queue works better when each item says what someone needs to resolve.

Give each expense a clear explanation.

An amount becomes easier to review when the source, purpose and person responsible stay together. Build a routine that catches ambiguity before it grows into a backlog.

Check whether the receipt image is readable.

A saved image is not useful evidence when its amount or reference cannot be read.

Preserve the complete document.

A useful crop for a message should not become the only retained version of a source.

Use filenames that help retrieval.

A filename should provide useful context without becoming a substitute for the document itself.

Match the attachment to the record.

The right amount beside the wrong attachment creates a misleading appearance of completeness.

Build an index that points to sources.

An index helps people find evidence; it should not duplicate every detail into a second uncontrolled record.

Separate versions without losing the original.

A corrected export and an original source should not compete under the same ambiguous filename.

Retain the relevant email context.

An attachment may need the message around it to explain why it was supplied.

Keep review notes separate from source evidence.

Annotations help interpretation, but they should not appear to be part of the original document.

Test whether someone else can find the source.

A folder makes sense only if a teammate can use it without a private explanation.

Work through a document backlog deliberately.

Start by making the backlog visible rather than rushing every item into a guessed category.

Make the source easy to find.

A useful document collection preserves the original evidence and helps someone retrieve it without knowing who saved the file. These guides cover practical habits around receipt and attachment organization.

Keep gross activity separate from net settlement.

A smaller bank deposit can have a clear explanation without implying that the original activity amount was wrong.

Review a settlement as a batch.

A single deposit may represent several underlying transactions and adjustments.

Keep pending activity distinct from confirmed evidence.

A pending label describes uncertainty that should remain visible in the review.

Use a reference as a matching clue.

A stable reference often narrows the search more reliably than a familiar amount.

Read a reversal alongside the original event.

A reversal needs a relationship to the activity it affects, not just a negative sign.

Keep the fee explanation with the amount.

A deduction needs a source description before it can be meaningfully reviewed.

Show the sequence of payment dates.

Activity date, settlement date and bank posting date can describe different stages.

Make an apparent overpayment a question.

An amount above an invoice total needs explanation before anyone decides what to do with the difference.

Explain a short payment before changing the balance.

A smaller receipt may reflect a partial payment, deduction or mistaken match.

Assemble a payment review pack.

A compact set of connected sources helps a reviewer understand an event without repeating the search.

Understand what the payment record says.

A payment, an invoice and a settlement answer different questions. These guides help retain the connections without counting the same event twice or assuming money moved because a screen changed.

Check the statement period first.

A correct amount from the wrong period can lead to a misleading comparison.

Confirm which account the statement describes.

Similar account names can conceal different underlying sources.

Reconcile the simple movement between balances.

An opening and closing amount provide boundaries for checking the activity between them.

Preserve the original statement description.

A friendly label can help readability while the original wording remains essential for tracing the source.

Check for overlapping statement imports.

Overlapping files can repeat entries even when each file is individually valid.

Trace both sides of an internal transfer.

A movement between two accounts should not be mistaken for two unrelated business events.

Give an unexplained statement line an owner.

An unfamiliar entry is easier to resolve when its known facts and next question are recorded together.

Check statement completeness before comparing totals.

A partial statement can make valid activity appear to be missing.

Make the sign convention explicit.

Different exports can show money in and money out using different columns or signs.

Write a useful statement review note.

The note should tell the next reviewer what was checked and what remains open.

Review the statement in context.

A statement is a source with a period, account and set of entries. Start with those boundaries before matching amounts or explaining differences.

Agree what this month-end review covers.

A shared scope prevents two people from doing different work under the same “month-end” label.

Build a source checklist before checking balances.

The first question is whether the review has the documents it needs.

Collect cut-off questions without guessing the answer.

An event near a period boundary may need more context than the document date alone provides.

Explain a balance difference before resolving it.

A difference is a clue to investigate, not a number to hide in a miscellaneous line.

Prioritize by the question that blocks progress.

The oldest item is not always the one preventing the next review step.

Prepare an adjustment request with evidence.

A reviewer needs to see the reason for a proposed change, not just its desired total.

Use status labels with a shared meaning.

Ready for review, approved and complete should describe different states when the work requires them.

Hand over the close without a memory test.

A good handoff lets the next reviewer continue from the actual state of the work.

Make a change after review visible.

A later document can affect work that someone has already checked.

Improve the next close from actual friction.

Small repeated obstacles are better improvement targets than an entirely new process every month.

Make month-end a sequence of clear checks.

A useful close routine shows what is ready, what is missing and which decisions belong to a reviewer. The aim is an understandable handoff rather than a last-minute search through scattered records.

Give the draft a clear brief.

A short brief tells the writer what the document must help someone do.

Separate supplied facts from inferred wording.

A fluent paragraph can make an unsupported assumption difficult to notice.

Write for the person receiving the document.

Internal shorthand can make a correct summary hard for another person to use.

Organize a summary around the review question.

A clear structure helps the reader separate facts, uncertainty and a proposed next step.

Resolve missing fields before release.

A blank or copied field can survive several rounds of editing unless someone explicitly checks it.

Keep the wording clear and proportionate.

A routine accounting message should explain the task without adding promises or pressure the source does not support.

Compare changed drafts by meaning.

A revised document can alter a fact even when most of its wording stays the same.

Make an approval request specific.

The reviewer should know exactly what decision is being requested and which version it concerns.

Check the exported document itself.

A correct editing screen does not guarantee a complete or readable export.

Retain the accepted draft and its context.

The useful archive is the version people acted on, together with enough context to understand its approval.

Make a draft easier to review.

A useful draft carries the purpose, source facts and unanswered questions into a clear document. Preparation should make the reviewer’s job easier without implying that the draft has already been approved.

Give one unresolved question a clear owner.

Several people seeing a message does not establish who will answer it.

Write a handoff someone can act on.

A useful summary starts with the current task, not the entire history of how it arrived.

Ask a question the reviewer can answer.

A precise question reduces the amount of investigation another person must repeat.

Keep the reason beside the decision.

A decision without its context can be difficult to apply consistently later.

Prepare a useful coverage handoff.

Someone covering your work needs the next actions and source locations, not access to your memory.

Use the review meeting for decisions.

The meeting is more useful when participants can see the evidence before discussing the question.

Ask for the access needed for the task.

A reviewer should receive appropriate access to relevant sources without unrelated credentials or documents.

Escalate with the checks already completed.

A second reviewer should not have to repeat the first person’s entire investigation.

Make a shared checklist show actual progress.

A checkbox is useful when everyone understands what evidence allows it to be checked.

Confirm the handoff was understood.

Sending a task and having another person accept its next action are different events.

Give the next person enough context.

Accounting work often moves between the person with the source, the person preparing the record and the person reviewing it. A clear handoff keeps those responsibilities connected without leaving decisions implied.

Ask for one clear result.

A focused request makes it easier to tell whether the answer is useful.

Supply the context that changes the answer.

A useful prompt includes the facts that distinguish this task from a generic example.

Ask the agent to identify missing facts.

A useful response can be a list of questions rather than a finished-looking document.

Check an AI-produced calculation independently.

A correct-looking explanation does not replace checking the inputs and arithmetic.

Check the source behind a specific answer.

A statement about your records needs traceable support rather than confidence alone.

Review what changed in an AI rewrite.

A smoother sentence can accidentally alter a factual detail or commitment.

Summarize open items without closing them.

A concise summary should preserve the unresolved nature of the work.

Ask for a comparison with clear boundaries.

A comparison is easier to review when the two sources and relevant fields are explicit.

Keep the final decision explicit.

A prepared answer and an approved business action should not share an ambiguous status.

Give a corrective follow-up with evidence.

When an answer misses the task, a specific correction is more useful than asking for a different tone alone.

Give your AI agent a better starting point.

Clear context and thoughtful review make an AI-assisted draft more useful. These guides focus on asking answerable questions, checking the result and retaining human control over the next step.

Retain the original currency amount.

A converted summary is easier to verify when the source amount remains visible.

Read the direction of the rate.

The same pair of currency names can be expressed in opposite directions.

Keep the rate date with the calculation.

A number labelled “exchange rate” is incomplete without the context of when and where it came from.

Keep unlike currencies out of one unexplained total.

A list can be numerically added while producing a total that has no clear meaning.

Explain the rounding in a worked conversion.

Small differences can come from rounding at different stages of a calculation.

Separate receipt currency from card-statement currency.

A purchase source and its statement entry may show different currencies and amounts.

Keep conversion and fees separate when sources do.

A difference between amounts may have more than one component.

Review a request to change document currency.

Changing the currency label alone does not convert an agreed amount.

Compare periods on a clearly labelled basis.

A changed converted total may reflect more than a change in underlying activity.

Assemble the context for a currency question.

A reviewer needs more than two different totals to explain an international record.

Keep the currency context with the number.

International records become easier to understand when original amounts, converted examples and source rates remain distinct. These guides explain the information a reviewer needs without prescribing a tax or accounting treatment.

Use a stable project reference across records.

A shared reference helps connect an agreement, invoice and expense without relying on similar filenames.

Retain the source behind a scope change.

Extra work should have context before it becomes an extra invoice line.

Keep milestone evidence beside the billing question.

A project milestone should be tied to the evidence your agreement uses to recognize it.

Review the context behind a time record.

A total of hours is easier to check when the task and agreement are clear.

Explain why a supplier cost belongs to a project.

A project code is more useful when its connection to the purchase can be understood.

Keep an estimate distinct from a confirmed record.

A planning number can look authoritative when it is copied into the same table as actual source amounts.

Hand over project records before the context disappears.

The person preparing the accounting record may not have attended the project conversations.

Connect a project payment to its document.

A project label alone may not identify which invoice or stage a receipt concerns.

Assemble a clear project close pack.

Finishing the work and finishing its records are related but separate tasks.

Improve the next project’s record routine.

Use specific record problems to improve the next handoff without redesigning the whole process.

Connect the records to the work.

Project work creates agreements, changing scope, supplier costs and handoffs. Keep those records connected so someone reviewing an amount can understand which piece of work it describes.

Make more room for your life.Powerful accounting, with an AI agent by your side.

Launch access Explore the guides

Bookkeeping

Invoices and income

Financial perspective

People and your agent

More

By business

By routine

More

Provider context

Platform

Related guides

More

Learn

Work better

Company

More

A little knowledge. A clearer next step.

Choose the task in front of you

Use examples as a way to reason

Make more room for your life.Powerful accounting, with an AI agent by your side.