Wedding supplier paperwork: keep the quote, payments, and open questions separate



A planning spreadsheet can help organize supplier paperwork, but it should not quietly turn a bank transfer into proof that a wedding service has been booked or delivered. Quotes, messages, payment records, and booking confirmations answer different questions. This is an invented worksheet exercise, not a testimonial about this studio, an actual couple's budget, a reservation request, or legal advice. All names, amounts, and document references in the example are fictional. You can practise the workflow locally without sharing real financial records or contacting any supplier.



Start with the document, not the reassuring label



A row named deposit paid can sound more conclusive than the source supports. Ask what document establishes the amount, who issued it, and what question it answers. A bank debit may show that money left an account. It does not establish which package was agreed, whether a date is available, what changes were accepted, or how any cancellation terms apply. Keep a separate status for each question. Avoid using one green cell as a substitute for the confirmations and professional advice a real arrangement may require.



Use a small fictional scenario



Imagine a training quotation initially listing 1,000.00, followed by a fictional revised version listing 950.00. The example bank table contains two outgoing payments, 300.00 and 500.00, for a combined movement of 800.00. If the revised training amount is the relevant comparison, the arithmetic difference is 150.00. That calculation does not create a debt, establish contract terms, or imply that a service has been confirmed. It simply gives the worksheet a checkable set of invented numbers and makes the difference between document versions visible.



Create a source register with versions



Assign neutral identifiers such as QUOTE-A-V1, QUOTE-A-V2, BANK-A, and MESSAGE-A. Record the document type, date as written, version, and the question it can support. Do not overwrite the first quotation with the revised one and then forget that a change occurred. A working table can point to the version you reviewed while retaining the earlier version in the source register. If a real document's status is unclear, label it unclear rather than choosing the version that produces the most convenient remaining-balance calculation.



Keep payment movement and planning status apart



Use one table for the fictional bank movements and another for planning questions. The movement table can contain source row, date, description, debit, credit, and review note. The planning table can list the relevant quotation version, message reference, unresolved question, and next normal follow-up. Do not automatically mark a service confirmed when a payment row appears. That separation is especially helpful when several people organize the same folder and might otherwise mistake a numerical check for a complete review of the underlying arrangements.



Preserve the raw extraction



Keep a Raw tab containing the first transcription or conversion and a Review tab for checked values. Retain a source identifier beside each row so that sorting does not break the trail. If a description is wrapped over two lines or an amount contains a questionable decimal separator, leave the original value intact and explain the reviewed interpretation separately. Corrections should be understandable later. A table that looks tidy after silent edits may be less useful than a less polished one whose assumptions and changes are explicitly documented.



Handle dates with care



A quotation date, message date, bank posting date, and proposed event date are different kinds of dates. Keep them in separate columns when they matter. Retain the date as written before adding a normalized form, and flag an ambiguous day-month order rather than guessing. A spreadsheet format can make a wrong date look perfectly respectable. Do not publish a real couple's event date, venue, address, or financial history as part of a public demonstration. The fictional exercise needs no identifying information to illustrate the method.



Check the arithmetic from the correct perspective



For the training bank table, both 300.00 and 500.00 are outgoing payments from the same fictional perspective, so the total outflow is 800.00. Keep the 150.00 difference in a separately labelled comparison column, not as an invented bank movement. A common mistake is to add the remaining amount as though it had already been paid, making the bank table match a quotation rather than the source statement. Review what each column means before trusting any total. The worksheet should describe observations rather than manufacture a satisfying story.



Do not merge rows because their wording matches



Two transfers may have the same description but refer to different dates or arrangements. Compare source identifiers and row references before calling something a duplicate. In a disposable test copy, duplicate the fictional 300.00 row and observe the change in the total. Then document why the test duplicate was removed from the reviewed view. Keep the raw source unchanged. Matching an expected quotation amount is not sufficient evidence that a bank row is duplicated, and deleting a row simply to reach that expectation would undermine the review.



Use conversion to prepare a reviewable table



Bank Statement Converter is an optional resource for a bank statement converter to excel workflow and other structured exports. Its public pages describe PDF and image inputs, Excel, CSV, and JSON outputs, individual and batch conversion, and separate, ZIP, or merged downloads. The public pricing page lists paid subscriptions and permanent page-credit packs. No purchase is required for this fictional exercise. Conversion can help reduce retyping, but an export is not a booking confirmation, an authenticity certificate, or a substitute for checking the source rows.







Product illustration only, not a wedding photograph, supplier quotation, booking confirmation, or customer financial record.



Inspect the reopened file



Open a disposable CSV copy and look for changed date interpretation, decimal separators, quotation marks, blank values, and identifiers that have lost leading zeros. Keep imported descriptions as text rather than permitting a value that resembles a spreadsheet formula to execute. Use a workbook when you need to preserve review notes, formulas, or status columns, because a plain CSV will not retain every workbook feature. Record the import settings so a second reviewer using different regional defaults can understand how the same source became the displayed table.



Share only what the recipient needs



In a real, authorized review, a recipient may not need an entire bank statement to answer a narrow payment question. Follow the recipient's established secure document process, minimize unrelated information, and keep the authorized original protected. If a working copy is redacted, verify that the method actually removes the information rather than merely covering its appearance. Do not upload real statements to an external service without considering current privacy and retention information and obtaining appropriate permission. This exercise deliberately uses fictional local data so no such disclosure is necessary.



Write open questions in neutral language



A useful handoff might say that the training table contains two outgoing movements totalling 800.00, while the revised fictional quotation lists 950.00. It should then identify which document would be needed to answer any remaining planning question. Do not imply seller misconduct, service quality, a couple's consent, or a completed booking from those numbers alone. If a real arrangement involves contract interpretation, tax treatment, a dispute, or professional financial decisions, seek appropriately qualified advice rather than asking a spreadsheet total to decide the matter.



Finish with traceability rather than visual polish



The exercise is complete when another reader can trace both fictional payments to their source rows, identify which quotation version was compared, reproduce the 150.00 arithmetic difference, and distinguish an unresolved planning question from a checked bank movement. Keep the raw table, review table, source register, and correction notes together. If a reader cannot explain a change, improve the note before improving the colors. A modest worksheet with clear boundaries is more useful than a polished dashboard that suggests the documents establish more than they actually do.