Invoices, payments & contracts

Wedding Computer includes invoicing inside your CRM. You can create and send invoices to couples, accept a booking-fee card payment through your own Stripe account, record manual payments, attach your default service contract, and collect a typed-name acceptance — without leaving the platform.

Creating an invoice

Go to Invoices → New invoice, or create one from within a contact or wedding workspace.

An invoice is made up of:

Line items — services, with name, quantity, unit price, and an optional description
Booking fee — a deposit, set as a fixed amount or a percentage of the total. This appears as the first due payment and is highlighted as the initial commitment amount.
Payment schedule — add multiple instalments, each with its own amount and due date
Tax — applied automatically based on your tax settings (label, rate, and whether it’s inclusive or exclusive of the listed prices)
Card processing fee — optionally passed to the client as a percentage, to cover Stripe’s fee
Notes — additional terms, instructions, or messages visible to the couple

Once sent, the couple receives a notification with access to the invoice and its secure booking page. The booking page is where they review the invoice, complete your booking questions, and accept any attached contract. If Stripe is connected and a booking fee is due, confirming can continue into Stripe Checkout.

Invoice statuses

Status	Meaning
Draft	Created but not yet sent
Sent	Sent; awaiting payment
Partial	At least one payment received, balance outstanding
Paid	Fully paid
Overdue	A payment due date has passed
Cancelled	Invoice voided
Refunded	Payment has been returned

Cancelled and Refunded exist as record statuses, including for imported or historical data. The current app does not initiate a Stripe refund, provide a vendor control to mark an invoice refunded, or reconcile Stripe refund events back into Wedding Computer automatically. Handle the refund in Stripe or through the original manual payment method and keep the couple informed; do not rely on the Wedding Computer status as proof that a refund completed.

Accepting card payments with Stripe

Wedding Computer uses Stripe Connect Standard — you connect your own Stripe account, and all card payments go directly into it. Wedding Computer does not charge a percentage of your invoices or take a cut of any payment.

To accept the booking fee by card, go to Settings → Payments → Connect Stripe and complete Stripe’s onboarding. After the couple confirms the booking form and contract, Wedding Computer can send them to Stripe Checkout for the pending booking-fee instalment. Later instalments remain on the payment schedule for you to track; record them manually when received.

Stripe handles all card verification, 3D Secure, and payment confirmation. You’re notified when a payment lands.

If you want to add a card surcharge, enable the card processing fee setting under Settings → Payments. The configured percentage is shown in the invoice totals. Check the card-surcharge rules that apply in your jurisdiction and Stripe account before enabling it.

Recording manual payments

For bank transfers, PayID, cash, or any other payment method, use Record payment on the invoice. Enter the amount, date received, and payment method. The invoice status updates automatically and the payment appears in the payment history.

Manual payments are not processed through Stripe — they’re records for tracking purposes only.

Service contracts

Wedding Computer keeps one default service-contract template for each vendor, and it attaches itself automatically to every new invoice you create. That’s the point of it: you don’t have to remember to bring a separate contract into every booking, and every couple you invoice is covered by your terms from the moment you send the invoice — not just the ones you remembered to chase for a signature.

To set this up: go to Settings → Contracts to create your contract template in your own words. Wedding Computer doesn’t provide legal templates — you write your own terms and conditions. Have any contract wording reviewed by a lawyer qualified in your jurisdiction before using it with clients.

Editing your default template later does not rewrite contracts already attached to earlier invoices, so a couple’s accepted terms stay exactly as they agreed to them, even if you update your wording afterwards.

The booking page asks the couple to type their full name, provide an email address, and tick that they agree to the contract. Wedding Computer records the typed name, email address, IP address, and timestamp against the invoice, and the confirmation email includes a text copy of the accepted contract — so if a dispute ever comes up, you have a timestamped record of exactly what was agreed to and when. This is a typed acceptance, not a drawn signature, and the service-contract record is not currently offered as a downloadable signed PDF. (Celebrants have a separate, dedicated PDF signing flow for NOIMs and other documents that need an in-order, witnessed signature — see Collaborative PDF signing below.)

The booking page

Every sent invoice has a booking link — a single, secure URL you share directly with the couple. Instead of sending a contract link, an invoice link, and a payment request as three separate emails, everything happens in this one flow. On this page they can:

Review the full invoice and payment schedule
Read and accept the contract with their typed name (if one is attached)
Fill in a booking form (if you’ve created one)
Continue to Stripe Checkout for the booking fee when card payment is configured

Because reviewing, signing, answering your booking questions, and paying all happen in one place, the couple confirms once and the booking moves straight from enquiry to signed and paid — without you following up across multiple emails to get each piece done.

The booking page can be embedded on your website by appending ?embed=1 to the URL and dropping it into an <iframe>.

Collaborative PDF signing (celebrants)

Celebrants have a dedicated workflow for signing NOIMs and other documents that require both celebrant and couple to sign in a specific order:

The celebrant prepares the PDF — either uploaded or exported from Wedding Computer’s NOIM generator
The celebrant releases the document to the couple
The couple signs via their workspace (using a browser canvas — no app download needed)
The couple’s signature is burned into the PDF
The celebrant counter-signs, completing the document
The fully signed PDF is stored under the celebrant’s access only

The order is enforced: the celebrant must release before the couple can sign, and the couple’s signatures lock the document before the celebrant’s counter-signature is accepted. The software is designed for a witnessed signing workflow, but the celebrant remains responsible for confirming that the process and document meet the legal requirements in their jurisdiction. The couple does not receive the final PDF through this workflow; it remains under the celebrant’s access.