Hand over an invoice query without losing the next action |

An invoice question can pass through several people before anyone can answer it. Sales knows what the customer ordered, the warehouse has the delivery reference, and the bookkeeper needs both. When one colleague goes on leave, a message saying “please follow up” leaves the next person to reconstruct the conversation.

Keep the invoice, changes to it and the payment record in your accounting system. A separate query list can hold the question, the person taking the next step and the date they will check it again. This gives a handover a clear purpose without creating another version of the accounts.

Write the question before assigning it

Take a fictional example: invoice INV-042 covers a delivery that the customer says arrived in two parts. “Invoice problem” is too vague. “Ask the warehouse to confirm the reference for the second delivery” tells the next colleague what evidence is missing. Add the latest confirmed fact underneath, with the date it was checked.

For a small team using Notion, a table of queries can start with these fields:

Invoice reference: a Text property containing the reference used in the accounting record.
Question and next action: short Text properties. Keep the unanswered question distinct from the action someone has agreed to take.
Responsible colleague: a Person property for someone in the workspace, or a Text field naming the responsible role.
Follow-up date: a Date property for the next internal check. Label it clearly so nobody mistakes it for the invoice payment deadline.
Query state: a Select property with options such as Open, Waiting for reply, Ready for review and Closed.

Point colleagues to the accounting record or its approved internal location. Copying the entire invoice into a broadly shared task list can expose customer details and leave an outdated document beside the current one.

Connect repeat customers when it saves a lookup

If your workspace already has a Customers database, a Relation property can connect a query to the correct customer page. The walkthrough on connecting client and work records in Notion explains this database structure. Apply that pattern to Customers and Queries, selecting the customer for each query yourself. The relation does not connect Notion to your accounting software or import invoice records.

A customer connection is useful when several questions concern the same business. For occasional queries, a reference and a clear next action may be sufficient. Add a second database only when the team will maintain it; a partly filled customer list gives the person receiving the handover another thing to check.

Make the transfer explicit

Before handing over INV-042, record what has already been checked, who was contacted and what is still missing. For example: “Customer confirmed the first delivery on Monday; warehouse reference for the second delivery still needed.” Replace the responsible colleague and agree a follow-up date with that person. A name in a field is not confirmation that someone has accepted the work.

Ask the receiving colleague to open the source record and explain the next step back to you. If they cannot access the necessary evidence, resolve that through the normal internal process before you leave. Do not copy restricted documents into the query list just to make the link easier to open.

Close the query with a short evidence note

When the question is answered, add the answer, its source and any action that still belongs in the accounting system. The colleague responsible for the accounts should check that record before the query is closed. Closed means the question has been resolved; it does not establish that an invoice has been paid.

Once this handover works for a few real queries, NotionSolutions’ guides to databases and shared work can help you develop the workspace further. Review which fields the team actually updates before adding more. The useful test is whether a colleague can pick up an unfinished question without asking you to repeat its history.