BaseCloud Accounting¶
Overview¶
The BaseCloud Accounting task works with the quotes, invoices, credit notes and payments in your BaseCloud account: the same ones on a client's Accounting tab and the Accounting page. See Quotes & invoices.
Actions
| Action | What it does |
|---|---|
| Create Quote, Create Invoice | Makes a quote or invoice from lines you give it. |
| Fetch Quote / Invoice | Reads one document, with its PDF link and payment link. |
| Edit Quote / Invoice | Changes one unpaid document's layout, due date or Reference, and any document's quote and invoice fields. |
| Mark Quote / Invoice Paid | Records a payment on an invoice: all it owes, or part of it. |
| Get Quotes / Invoices | Finds every document that matches your criteria, to loop over. |
| Void Quote / Invoice | Voids one unpaid document. |
| Reconcile Invoice | Reconciles one invoice that is paid in full. |
| Create Credit Note | Credits an invoice, writes one off, or makes a credit note on its own. |
| Send Statement | Emails a client their statement. |
| Post Journal | Posts a manual journal in your books. |
| Record Money Spent / Received | Records money in or out of a bank account in your books. |
Old documents. Give a quote, invoice, credit note or payment its own date and its number in your old system, run an import again without making copies, and start no automations for it. See Bringing old documents over.

Before you start¶
- A layout set. Quotes and invoices are printed with a layout set from Settings → Quote/Invoice Layout. Pick it in Invoice Layout.
- The client. Every document belongs to a client. Map the client's ID from the trigger or an earlier step, such as Match to Client.
- Quote and invoice fields are optional. Create Quote, Create Invoice and Edit Quote / Invoice can fill in your quote and invoice fields, the fields your reports split sales by included. See Filling in quote and invoice fields.
How the task reads what you give it¶
These rules apply to every action.
Dates can be YYYY-MM-DD (2026-11-30) or DD/MM/YYYY (30/11/2026), with or without a time. A date and time
from another system (2026-11-30T23:15:00Z) is read as the day it was in your business's timezone (Settings →
General). Anything else stops the run and names the value. Use the Date Formatter task to turn
other formats into one of these. A blank date means today, in your business's timezone.
Amounts, quantities, prices and tax rates may include a currency symbol or code, thousands separators, a decimal
comma or a %: $1,250.00, R 1 250,00, 1.250,00, 15% and 8.25 are all read correctly. Quantities can have up
to 4 decimal places, such as 1.5 hours. Anything that can't be read as a number stops the run with the reason,
rather than becoming 0.
Lists. Lines are given as lists separated by |, one entry per line, in the same order: Design|Build|Test.
Every list (quantities, prices, tax rates, discounts) must have one entry per description, or the run stops. Leave an
entry empty for its default (quantity 1, price 0, no tax, no discount).
A setting whose variable comes out empty stops the run. If you map a date, an amount, a document number, a client or another setting to a variable, and that variable is empty when the workflow runs, the task stops and says which setting was empty. It isn't read as "today" or "the whole balance". Settings where blank only means "none" (how it was paid, a payment's Reference, a document's Reference, a statement's email address) are read as none.
When a run stops, nothing is saved, run_text says why and what was not done, and the tasks after it don't run.
Outputs¶
A quote or invoice fills the quote_invoice_* fields; line fields are | lists, one entry per line. Reference fields
as {{task_<ID>_<field>}}. Only the fields the action uses are filled: check a real run in the OUTPUT panel before
using one downstream.
| Field | Notes |
|---|---|
client_id |
The client the document belongs to. |
quote_invoice_id |
BaseCloud's ID for the document. |
quote_invoice_o_id |
The document number, e.g. 1042. |
quote_invoice_o_id_full |
The number with its prefix, e.g. QU1042 or INV1042. |
quote_invoice |
Quote or Invoice. |
quote_invoice_status |
Unpaid, Paid or Void. A part-paid invoice reads Unpaid, because money is still owed. |
quote_invoice_payment_status |
Unpaid, Part Paid, Paid, Credited (settled by credit notes alone, such as a write-off) or Void. |
quote_invoice_amount_paid |
What has been paid, e.g. 250.00. |
quote_invoice_balance_due |
What is still owed, e.g. 832.50. Empty on a quote. |
quote_invoice_date_paid |
The day it was paid in full; empty while anything is owed. |
quote_invoice_reference |
Its Reference, such as its number in your old system. Empty when it has none. |
quote_invoice_field_<id>, quote_invoice_field_<id>_value |
Each of your quote and invoice fields on the document: as a person reads it, and as stored. Empty when the field is. |
quote_invoice_date |
Its date: a quote's quote date, an invoice's invoice date. |
quote_invoice_date_created |
When it was made. A quote turned into an invoice keeps the day it was quoted. |
quote_invoice_expiry_date |
A quote's expiry date, or an invoice's due date. |
quote_invoice_sub_total, quote_invoice_total |
Total before tax, and with tax. |
item_description, item_code, item_quantity, item_unit_price, item_tax_rate |
The lines. |
item_details |
The details under each line; empty for a line with none. A \| typed in the details is written as /. |
item_description_with_details |
Each description with its details on the lines below it. Map this where there is one text field per line, such as Xero's Description(s). |
tracking_category_1_label, tracking_category_1_value, tracking_category_2_label, tracking_category_2_value |
Older names, kept so workflows made before tracking categories became line fields keep working. They hold each line's answer in the line field each tracking category became: its option's name, and its option's ID, joined with \|. A line with no answer reads null. For a new workflow, use that line field's own outputs (quote_invoice_line_field_<id>). |
document_url |
A link to the PDF. The PDF is made the first time the link is opened, so it always shows the document as it is then. |
doc_name |
A file name for the PDF. |
payment_link |
The page where the client sees and pays the document. |
payments |
Every payment on the invoice, oldest first: each one's payment_id, amount (the part on this invoice), date, method, method_code, gateway, reference and currency. Empty on a quote, or an invoice nothing was paid on. Credit from a credit note isn't listed. |
payment_count, payments_total |
How many payments, and what they come to. |
To work out by how an invoice was paid, compare each payment's method_code (card, cash, ach, eft,
gateway, custom_3…), which stays the same when a payment method is renamed. Loop over
{{task_<ID>.JSON.payments}}, or hand it to a Code task. See
How the invoice was paid.
Every run also gives run (whether the task succeeded) and run_text (what happened, or why it stopped). Each
action below lists the extra fields it gives.
Settings¶
| Setting | Actions | What to enter |
|---|---|---|
| Action | all | Which action to run. |
| Quote / Invoice ID | Fetch, Edit, Mark Paid, Void, Reconcile, Create Credit Note | One BaseCloud number: INV1024, QU1024, #1024 or 1024. |
| Or find it by its Reference | Mark Paid, Create Credit Note | Its number in your old system (its Reference). Fill in Client ID too. |
| Client ID | Create Quote / Invoice / Credit Note, Send Statement; optional on Mark Paid and Record Money | The client's ID. |
| Invoice Layout | Create Quote / Invoice / Credit Note | The layout set it's printed with. |
| Layout, Due / expiry date, Reference | Edit | What to change; blank keeps it. See Edit Quote / Invoice. |
| Your quote and invoice fields, one setting each | Create Quote / Invoice, Edit | What to fill in; blank fills in nothing (Create) or keeps it (Edit). See Filling in quote and invoice fields. |
| Prices are | Create Quote / Invoice / Credit Note, Record Money | As in my settings (your Invoice prices are setting), Tax exclusive, Tax inclusive or No tax. |
| Item Description(s) … Discount(s) % | Create Quote / Invoice / Credit Note | The lines, as \| lists. |
| Date | Create Quote / Invoice, Post Journal, Record Money | The document's own date. Blank: today. |
| Credit note date | Create Credit Note | Blank: today. |
| Due / expiry date | Create Quote / Invoice | Blank: an invoice is due by your payment terms (7 days if you haven't set any); a quote expires 7 days after its date. |
| Reference | Create Quote / Invoice / Credit Note | Free text, up to 100 characters: usually its number in your old system. |
| If the client already has this Reference | Create Quote / Invoice / Credit Note | Use that document (the default) or Create a new one. |
| Expected total (optional) | Create Quote / Invoice | The total it must come to, tax included. |
| Tax amount (optional) | Create Quote / Invoice | The tax on the document in your old system. |
| Old document: don't start automations | Create Quote / Invoice / Credit Note, Mark Paid | Automatic: only when dated more than 30 days ago (the default), Yes, never start them, or No, always start them. |
| Date paid, Amount, Keep anything above the balance as credit, How it was paid, Reference | Mark Paid | See Mark Quote / Invoice Paid. |
| Amount to credit, Write off, Reason | Create Credit Note | See Create Credit Note. |
| Statement, From, To, Send to (optional) | Send Statement | See Send Statement. |
| What it is for, Reference (optional), Accounts, Debits, Credits, Amounts, Tax rates, Line descriptions, Bank account, Money in or out | Post Journal, Record Money | See Post Journal and Record Money Spent / Received. |
Builder fields¶
The Field column is the label as it appears in the task builder; Key is the name the value is stored under and referenced by.
| Field | Key | Type | Default | Notes |
|---|---|---|---|---|
| Action | accounting_action |
select | create_invoice |
Options: Create Quote · Create Invoice · Fetch Quote / Invoice · Edit Quote / Invoice · Mark Quote / Invoice Paid · Get Quotes / Invoices · Void Quote / Invoice · Reconcile Invoice · Create Credit Note · Send Statement · Post Journal · Record Money Spent / Received |
| Find quotes and invoices by | _invoice_match_rows |
invoice-match-rows | – | Only shown when accounting_action is get_quotes_invoices |
| Quote / Invoice ID | Quote/Invoice ID |
text | – | Only shown when accounting_action is fetch_quote_invoice, edit_quote_invoice, paid_quote_invoice, void_quote_invoice, reconcile_invoice, create_credit_note |
| Or find it by its Reference | Invoice Reference |
text | – | Only shown when accounting_action is paid_quote_invoice, create_credit_note |
| Date paid | Date Paid |
text | – | Only shown when accounting_action is paid_quote_invoice |
| Amount | Amount |
text | – | Only shown when accounting_action is paid_quote_invoice |
| Keep anything above the balance as credit | Keep Extra As Credit |
select | – | Options: No · Yes. Only shown when accounting_action is paid_quote_invoice |
| Amount to credit | Amount |
text | – | Only shown when accounting_action is create_credit_note |
| Write off | Write Off |
select | – | Options: No · Yes. Only shown when accounting_action is create_credit_note |
| Reason | Reason |
text | – | Only shown when accounting_action is create_credit_note |
| How it was paid | Method |
select | – | Only shown when accounting_action is paid_quote_invoice |
| Reference | Reference |
text | – | Only shown when accounting_action is paid_quote_invoice |
| Invoice Layout | invoice_var_id |
select | – | Only shown when accounting_action is create_quote, create_invoice, create_credit_note |
| Layout | invoice_var_id |
select | – | Options: Keep its layout. Only shown when accounting_action is edit_quote_invoice |
| Client ID | client_id |
text | – | Only shown when accounting_action is create_quote, create_invoice, create_credit_note, send_statement |
| Client ID (optional) | client_id |
text | – | Only shown when accounting_action is paid_quote_invoice |
| Client ID (optional) | client_id |
text | – | Only shown when accounting_action is record_bank_transaction |
| Prices are | Prices Are |
select | – | Options: As in my settings · Tax exclusive · Tax inclusive · No tax. Only shown when accounting_action is create_quote, create_invoice, create_credit_note, record_bank_transaction |
| Item Description(s) | item_Description |
text | – | Only shown when accounting_action is create_quote, create_invoice, create_credit_note |
| Item Details (optional) | item_Details |
text | – | Only shown when accounting_action is create_quote, create_invoice, create_credit_note |
| Item Code(s) | item_Code |
text | – | Only shown when accounting_action is create_quote, create_invoice, create_credit_note |
| Item Quantity(ies) | item_Quantity |
text | – | Only shown when accounting_action is create_quote, create_invoice, create_credit_note |
| Unit Cost(s) | item_Unit_Cost |
text | – | Only shown when accounting_action is create_quote, create_invoice, create_credit_note |
| Tax Rate(s) | item_Tax_Rate |
text | – | Only shown when accounting_action is create_quote, create_invoice, create_credit_note |
| Discount(s) % (optional) | item_Discount |
text | – | Only shown when accounting_action is create_quote, create_invoice, create_credit_note |
| Date | Document Date |
text | – | Only shown when accounting_action is create_quote, create_invoice |
| Credit note date | Document Date |
text | – | Only shown when accounting_action is create_credit_note |
| Date | Document Date |
text | – | Only shown when accounting_action is post_journal, record_bank_transaction |
| Due / expiry date | Due Date |
text | – | Only shown when accounting_action is create_quote, create_invoice |
| Reference | Document Reference |
text | – | Only shown when accounting_action is create_quote, create_invoice, create_credit_note |
| Due / expiry date | Due Date |
text | – | Only shown when accounting_action is edit_quote_invoice |
| Reference | Document Reference |
text | – | Only shown when accounting_action is edit_quote_invoice |
| If the client already has this Reference | If Reference Exists |
select | use |
Options: Use that document · Create a new one. Only shown when accounting_action is create_quote, create_invoice, create_credit_note |
| Expected total (optional) | Expected Total |
text | – | Only shown when accounting_action is create_quote, create_invoice |
| Tax amount (optional) | Tax Amount |
text | – | Only shown when accounting_action is create_quote, create_invoice |
| Old document: don’t start automations | Old Document |
select | – | Options: Automatic: only when dated more than 30 days ago · Yes, never start them · No, always start them. Only shown when accounting_action is create_quote, create_invoice, paid_quote_invoice, create_credit_note |
| Statement | Statement Type |
select | outstanding |
Options: What is owed now · Everything between two dates. Only shown when accounting_action is send_statement |
| From | Statement From |
text | – | |
| To | Statement To |
text | – | |
| Send to (optional) | Statement Email |
text | – | Only shown when accounting_action is send_statement |
| Money in or out | Bank Kind |
select | spend |
Options: Money spent · Money received. Only shown when accounting_action is record_bank_transaction |
| Bank account | Bank Account |
text | – | Only shown when accounting_action is record_bank_transaction |
| What it is for | Narration |
text | – | Only shown when accounting_action is post_journal, record_bank_transaction |
| Reference (optional) | Document Reference |
text | – | Only shown when accounting_action is post_journal, record_bank_transaction |
| Accounts | journal_Account |
text | – | Only shown when accounting_action is post_journal |
| Debits | journal_Debit |
text | – | Only shown when accounting_action is post_journal |
| Credits | journal_Credit |
text | – | Only shown when accounting_action is post_journal |
| Line descriptions (optional) | journal_Description |
text | – | Only shown when accounting_action is post_journal |
| Accounts | line_Account |
text | – | Only shown when accounting_action is record_bank_transaction |
| Amounts | line_Amount |
text | – | Only shown when accounting_action is record_bank_transaction |
| Line descriptions (optional) | line_Description |
text | – | Only shown when accounting_action is record_bank_transaction |
| Tax rates (optional) | line_Tax_Rate |
text | – | Only shown when accounting_action is record_bank_transaction |
Action 1: fetch_quote_invoice¶
Reads one quote or invoice: its details, lines, PDF link and payment link.
- Quote / Invoice ID: the document's number, such as
INV123,QU456or123. - No match:
foundisfalse,run_textsays "No quote/invoice found.", and the workflow carries on.
Gives the outputs above, plus found.
Action 1a: edit_quote_invoice¶
Edit Quote / Invoice changes the layout, due date or Reference of one quote or invoice, and its quote and invoice fields, as editing it in the client's Accounting tab does. To change its lines' descriptions, amounts or tax, edit it there.
| Setting | What to enter |
|---|---|
| Quote / Invoice ID | One BaseCloud number, such as INV1024, QU1024 or 1024, read the way Void reads it. |
| Layout | One of your layout sets. Keep its layout leaves it as it is. |
| Due / expiry date | The new due date, or a quote's expiry date. It can't be before the document's own date. Blank keeps it. |
| Reference | The new Reference, up to 100 characters. Blank keeps it. |
| Your quote and invoice fields | The new answers. Blank keeps what the document has, and so does a blank entry for a line. See Filling in quote and invoice fields. |
Set at least one of these (besides the number), or the task stops. A layout, due date or Reference mapped to a variable that comes out empty stops the run too, rather than being kept or cleared. A field whose variable comes out empty is kept as it is. This task can't empty a field.
What it does
- No match:
foundisfalse,run_textsays "No quote/invoice found.", and the workflow carries on. The task stops if two documents share the number, or if the number names the wrong kind (QU1024that has since becomeINV1024). - The layout, due date and Reference change only on a document with no money on it. A paid, part-paid, reconciled or void one stops the task with the reason, nothing is changed, and the tasks after it don't run. A credit note's aren't edited either.
- Fields can be changed on a paid invoice. A paid, part-paid or reconciled invoice, and a credit note, still take new answers in their quote and invoice fields, as they do in the CRM, because the answers change no amount. Only a void document refuses them. A line that already has the answer you give isn't changed, so running the task again on a paid invoice doesn't stop.
- When something changed, a note on the client lists what (such as "Edited layout from Standard to Modern"), and it
fires Quote/Invoice Edited. When the document already had those settings and answers, nothing is written and
nothing fires:
was_changedisfalse. So a workflow started by Quote/Invoice Edited that edits the same document stops there.
Outputs: the document as it is now (see Outputs), plus found and was_changed. run_text says
"Edited INV…." or "INV… already had these settings, so nothing was changed." A field left out is said after that (see
Filling in quote and invoice fields).
Action 2: paid_quote_invoice¶
Mark Quote / Invoice Paid records a payment on an invoice: the whole balance, or part of it. It does the same as Record payment in the CRM. A payment on a quote turns it into an invoice first.
| Setting | What to enter |
|---|---|
| Quote / Invoice ID | One BaseCloud number, such as INV1024 or 1024. |
| Or find it by its Reference | Or the invoice's number in your old system, with the Client ID. If you give both, they must name the same invoice. |
| Client ID (optional) | Needed to find the invoice by its Reference. With a number, the task stops if that invoice is another client's. |
| Date paid | The day the money arrived. Blank: today. A date after today is refused. |
| Amount | How much was paid. Blank: everything the invoice still owes. Less makes the invoice part paid. |
| Keep anything above the balance as credit | No (the default): only what's owed is recorded, and a note on the client says how much was left out. Yes: the rest is kept as the client's credit for their next invoice. |
| How it was paid | Pick one of your payment methods, or map a value: the name of one of your own methods (such as Venmo), or ach, wire, check (or cheque), eft (or bank transfer), cash, card, card_machine or other. Stripe, Paystack or Online read as an online payment. Blank or anything else is Other. |
| Reference | The bank or payment reference. With a Reference, running this again never records the same payment twice. |
| Old document: don't start automations | See Bringing old documents over. |
How it finds the invoice. A number must be one BaseCloud number. A number that starts with 0 (such as
INV-0042) is another system's numbering, and the task stops: map it to Or find it by its Reference with the
Client ID instead. The task also stops if two documents share the number, if two of the client's documents share
the Reference, if the invoice is another client's, or if the number is a credit note.
What it records
- No invoice found:
foundisfalse,run_textsays "No quote/invoice found.", and the workflow carries on. - Nothing owed (paid in full, or void):
already_paidistrue,run_textsays "Invoice already marked as paid.", and nothing is recorded. This is checked again at the moment of saving, so an invoice paid a second earlier, for example by a card charge in the same workflow, is skipped too. - With a Reference, if a live payment with the same Reference, amount and date is already on the client, nothing
new is recorded:
was_recordedisfalse, andrun_textsays "A payment with the Reference … was already recorded, so it was not recorded again." A re-run of an import never doubles a part payment. - Otherwise one payment is recorded:
- Less than the balance: the invoice is Part Paid, and
run_textsays "Recorded a part payment." - The balance or more: the invoice is Paid, and
run_textsays "Successfully marked invoice as paid." - More than the balance: with Keep anything above the balance as credit on Yes, the rest is the client's
credit (
payment_credit). Otherwise only the balance is recorded,payment_unrecordedsays how much was left out, and a note on the client says so.
- Less than the balance: the invoice is Part Paid, and
- It fires Payment received, and Marked as paid when the invoice is now paid in full, unless Old document says not to.
Outputs: the invoice as it is now (see Outputs), plus:
| Field | Notes |
|---|---|
found |
Whether the invoice exists. |
already_paid |
true when nothing was owed, so nothing was recorded. |
was_recorded |
false when a payment with the same Reference, amount and date was already recorded. |
payment_id, payment_amount |
The payment and how much it was. |
payment_credit |
What was kept as the client's credit. 0.00 unless Keep anything above the balance as credit is on. |
payment_unrecorded |
What was left out because it was more than the invoice owed. 0.00 when nothing was. |
quote_invoice_date_paid |
The day it was paid in full: the Date paid, or today. |
When it stops: the date isn't a date or is after today, the amount isn't a number above zero, the invoice can't be found unambiguously, or the payment is refused, for example because the invoice is reconciled or (with your books on) the date is on or before your lock date. A payment a workflow records is held to the lock date like one you record by hand. Use a later Date paid; while you're bringing old payments over, set the lock date only once they're in.
A new invoice can already be paid by credit
When a client has credit, a new invoice dated today uses it by itself. If the credit covers the invoice, a Mark
Quote / Invoice Paid straight after Create Invoice finds nothing owed and records nothing (already_paid is
true), so the money that just arrived isn't recorded. Check quote_invoice_balance_due from the create step,
or branch on already_paid and leave accounts a note.
Charging a card? You don't need Mark Paid
A Stripe or Paystack Charge Account step with the
invoice number in its metadata (invoice_id) charges what the invoice still owes, and records the payment by
itself when the card payment comes through. If a Mark Paid step runs after the payment has come through, it finds
nothing owed and skips. If it runs before, and the card payment arrives within the hour for the same amount, the
card payment takes Mark Paid's place, so the money is counted once and nothing runs twice. Leave Mark Paid out of
card workflows anyway, or use the Payment received event to carry
on once the money is in.
Action 2a: get_quotes_invoices¶
Get Quotes / Invoices finds every document that matches all the criteria you add, and returns their numbers for a Loop: for example, to chase or void each one.
Criteria (add a row for each; one row per kind):
| Criterion | Takes |
|---|---|
| Client ID | One client's ID. |
| Client status | A client status. |
| Type | Quote, Invoice or Credit note. |
| Paid status | Unpaid (anything still owed, part paid included), Paid (paid in full), Part paid or Overdue (still owing after its due date). |
| Date created, Date paid | A period: today, yesterday, this week, last 7 days, last week, this month, last 30 days, last month, this quarter, last quarter, this year, last year. |
| Created on or after / before, Paid on or after / before | A date. |
| Due on or after, Due on or before | A date. Invoices only. |
| Days overdue (at least) | A number of days, such as 7: unpaid invoices at least that many days past their due date. It can't be combined with Paid status other than Overdue. |
| Reconciled | Yes or no. |
| Created by | A user. |
| Search text | Text to look for in the document number, its Reference or a line's description. |
Dates follow your business's timezone. Date created is a quote's quote date and an invoice's invoice date: a quote turned into an invoice is found by the day it became one. An invoice with no due date is due 7 days after its date.
Credit notes are left out unless Type is Credit note. A row left blank is ignored, but a criterion that
can't be used stops the task rather than being dropped, since dropping it would widen the search (a Client ID
whose variable came out empty would otherwise return every client's documents). With no criteria at all the task
stops too. At most 10,000 documents are returned, the most recently added first, and run_text says so when the
limit is reached.
Outputs
| Field | Notes |
|---|---|
found |
Whether anything matched. The task completes either way: branch on this. |
quote_invoice_ids |
The numbers, comma-separated: what Fetch, Mark Paid and Void take. |
quote_invoice_count |
How many matched. |
quote_count, invoice_count, credit_note_count |
How many of each. |
total_amount |
Their total, tax included. Credit notes are taken off. |
currency_symbol |
Your currency symbol. |
matched_by |
The criteria used. |
Action 2b: void_quote_invoice¶
Void Quote / Invoice voids one unpaid quote or invoice, as Void on the Accounting page does. Nothing is deleted: the document stays, with the status Void.
- It reads one document number:
1024,INV1024,QU1024,INV-1024or#1024. Anything else (a list such as1024,1031, a decimal such as1024.00) stops the task. To void many, put this task in a Loop over Get Quotes / Invoices. - No match:
foundisfalse, and the workflow carries on. The task stops if two documents share the number, or if the prefix names the wrong kind (QU1024that has since becomeINV1024). - A document with money on it, or reconciled, is never voided. The task stops with "INV… is marked as paid, so it was not voided." (or "… is reconciled, so it was not voided.") and the tasks after it don't run. A credit note isn't voided here either. To reverse a real sale, use a credit note.
- It fires Quote/Invoice Deleted, only when this run voided the document.
Outputs: found, voided (this run voided it), already_void (it was void before; nothing changed),
client_id, quote_invoice_id, quote_invoice_o_id, quote_invoice_o_id_full, quote_invoice,
quote_invoice_status.
Action 2c: reconcile_invoice¶
Reconcile Invoice reconciles one invoice, as ticking Recon on the Accounting page does. A reconciled invoice is locked: nobody can edit it, record or remove its payments, or void it until the mark is taken off.
- It reads one invoice number, the same way Void does:
1024,INV1024,INV-1024or#1024. To reconcile many, put this task in a Loop over Get Quotes / Invoices with Paid status set to Paid. - No match:
foundisfalse, and the workflow carries on. The task stops if two documents share the number. -
Only an invoice paid in full is reconciled. Anything else stops the task, nothing is changed, and the tasks after it don't run:
- Unpaid: "INV… isn't paid, so it was not reconciled. Mark it paid first."
- Part paid: "INV… is only part paid, so it was not reconciled. Record the rest of the payment first."
- Void, a quote, or a credit note: "… is void / is a quote / is a credit note, so it was not reconciled."
This is checked again at the moment of saving, so a payment removed a second earlier stops the task too. 4. An invoice already reconciled is left as it is:
already_reconciledistrue, andrun_textsays "INV… is already reconciled." 5. It's reconciled today, in your business's timezone (Settings → General): the day the Accounting page shows next to Recon. 6. It starts no automations, as the Recon tick doesn't.
With your books on, invoices are reconciled by matching their payments to your bank lines in Bank reconciliation, so this action always stops, with "Your books are on, so invoices are reconciled by matching their payments to your bank lines in Banking."
Outputs: found, reconciled (this run reconciled it), already_reconciled, client_id, quote_invoice_id,
quote_invoice_o_id, quote_invoice_o_id_full, quote_invoice, quote_invoice_status. run_text says
"Reconciled INV…."
Action 3: create_quote¶
Create Quote makes a quote from the lines you give it.
| Setting | What to enter | Example |
|---|---|---|
| Client ID | Required. | {{client_id}} |
| Invoice Layout | Required. | – |
| Prices are | Blank uses your Invoice prices are setting. | Tax inclusive |
| Item Description(s) | Required. One per line. | Consulting\|Design work |
| Item Details (optional) | Text under each line. | Two workshops\| |
| Item Code(s) | With your books on, a code that names an account in your chart. | 4000\|4000 |
| Item Quantity(ies) | Blank is 1. Up to 4 decimal places. | 10\|2.5 |
| Unit Cost(s) | Blank is 0. | 150.00\|$1,200.00 |
| Tax Rate(s) | A percentage. Blank is no tax. | 15\|8.25% |
| Discount(s) % (optional) | A percentage off each line, before tax. | 10\| |
| Date | Blank: today. | {{task_36611_old_date}} |
| Due / expiry date | Blank: 7 days after the date. It can't be before the date. | 2026-03-31 |
| Reference | Usually its number in your old system. | QB-1042 |
| If the client already has this Reference | Use that document (the default) or Create a new one. | – |
| Expected total (optional) | The total it must come to, tax included. | 1150.00 |
| Tax amount (optional) | The tax in your old system. | 150.00 |
| Old document: don't start automations | See below. | – |
| Your quote and invoice fields | Optional: answers for the document, and for each line. See Filling in quote and invoice fields. | PO-7781 |
What it does
- With a Reference and Use that document: if the client already has a live quote with that Reference, or
the invoice that quote became (for Create Invoice, an invoice with that Reference), nothing is made. The task
carries on with that one,
was_createdisfalse, andrun_textsays "Found the existing document with Reference …". The document found must come to the Expected total and have the same Date, when you give them, or the task stops: that Reference belongs to a different document. This is checked at the moment of saving, so two runs at once can't both make it. - Otherwise it makes the quote with the next number (
QU…), dated Date (or today), expiring on Due / expiry date (or 7 days after the date), with the answers you gave in its fields. BaseCloud also keeps the day it was really entered. A document found by its Reference keeps the answers it has. - With an Expected total: if the lines don't come to it, to the cent, nothing is saved and the run stops.
- With a Tax amount: a difference of a cent or so per taxed line (an old system that rounded tax on the total) is moved onto the largest taxed line, so the document matches the old one exactly. A bigger difference stops the run.
- It fires Quote/Invoice Created, unless Old document says not to.
run_textsays "Successfully created document."
A document dated before today, or with a Tax amount, keeps the tax rates you gave it, even for a client with their own tax treatment (such as a tax-exempt client).
Outputs: the outputs above, plus was_created, document_date (YYYY-MM-DD), document_url and
payment_link.
When it stops: a date that isn't one, a line whose number can't be read, lists of different lengths, a field answer that can't be read, an expected total the lines don't come to, a tax amount too far from the lines' tax, a quote coming to less than zero, a date in a locked period, or (with your books on) a line with no account it can post to. Nothing is saved.
With your books on, a document dated before your books' start date is part of your opening balances, and one dated on or before your lock date is refused.
Action 4: create_invoice¶
Create Invoice works like Create Quote, and makes an invoice (INV…). The differences:
- Due / expiry date blank: due by your payment terms, or the client's own (7 days if you haven't set any).
- An invoice dated today uses the client's credit by itself. One dated in the past doesn't: record its real payment next, with Mark Quote / Invoice Paid and its Date paid.
- An invoice for 0.00 is marked Paid as soon as it's made. An invoice can't come to less than zero: make a credit note instead.
Filling in quote and invoice fields¶
Create Quote, Create Invoice and Edit Quote / Invoice have a setting for each of your quote and invoice fields, under the field's name. Type an answer or map a variable from an earlier step.
Document fields take one answer for the whole document, such as a PO number: PO-7781.
Line fields take an answer for each line, in the same order as the lines, separated by |, like the item lists. With three lines, Labour, Parts and Travel:
| You enter | Labour | Parts | Travel |
|---|---|---|---|
2026-12-01\|2026-12-02\|2026-12-03 |
1 Dec 2026 | 2 Dec 2026 | 3 Dec 2026 |
Service\|\|Service |
Service | (none) | Service |
Service\|Sales |
Service | Sales | (none) |
Service (no \|) |
Service | Service | Service |
One answer with no | is for every line. An empty entry, and any line past the last entry, gets no answer (on
Edit Quote / Invoice, that line keeps the answer it has). More entries than the document has lines stops the run.
How answers are read, as the client and contact tasks read them:
| Field type | Enter |
|---|---|
| Text, long text, location | The text. |
| Date | A date such as 2026-11-30 or 30/11/2026. |
| Time | A time such as 14:30, 9:30 or 2:30 pm. |
| Number, amount | A number. Symbols and separators are fine: $1,250.00. |
| Checkbox | yes or no (or true/false, 1/0). |
| Single choice | The option's name, in any capitals, or its ID. |
| Multiple choice | Option names or IDs, separated by commas: Cleaning, Repairs. |
| User | One of your team, by their full name, their email address or their user ID. |
An answer that can't be read (an option the field doesn't have, a date that isn't one, text in a number field) stops the run, names the field and the answer, and nothing is made or changed. It is never saved empty.
A field that has gone. If a field this task fills in has since been deleted, or is set in Settings to be on other
kinds of documents (say invoices only, and the task makes a quote), the task carries on without it, and run_text
says so after its usual words: "PO Number is not on quotes, so it was left out." or "A field this task sets no longer
exists, so it was left out." Remove the setting from the task to stop the message.
Workflows fill fields in as BaseCloud's system user, so a field's access level doesn't stop them.
Action 5: create_credit_note¶
Create Credit Note makes a credit note, as Credit and New credit note do in the CRM. It does one of two things:
- Credit an invoice: give its number in Quote / Invoice ID, or its old number in Or find it by its Reference with the Client ID. Amount to credit blank credits all that is left on it; an amount credits that much, spread over its lines. Write off set to Yes writes off what the invoice still owes, as money you won't collect.
- A credit note on its own: leave both empty, and give the Client ID and the lines, as on Create Invoice. All of it becomes the client's credit. This is how an old system's unused customer credit comes over.
| Setting | What to enter | Example |
|---|---|---|
| Quote / Invoice ID | The invoice to credit. | {{task_36613_quote_invoice_o_id_full}} |
| Or find it by its Reference | Its old number, with the Client ID. | INV-0042 |
| Client ID | With no invoice: who it's for. | {{client_id}} |
| Amount to credit | Crediting an invoice: how much, tax included. Blank: all that is left. | 250.00 |
| Write off | Crediting an invoice: Yes writes off what it still owes. | Yes |
| Reason | Why, kept and printed on the credit note. | Returned goods |
| Invoice Layout, Prices are, the item lists | With no invoice: the layout and lines, as on Create Invoice. | – |
| Credit note date | Blank: today. | 31/12/2026 |
| Reference, If the client already has this Reference | As on Create Invoice. | CN-207 |
| Old document: don't start automations | See below. | – |
It follows the same rules as the CRM: it can't credit more than is left on the invoice, credit a quote or a void invoice, or be dated in a locked period. When it can't, the run stops with the reason and nothing is made.
It fires Credit note created, unless Old document says not to. A write-off doesn't fire Marked as paid.
Outputs
| Field | Notes |
|---|---|
found |
true when the run finished. |
was_created |
false when the client already had a credit note with this Reference and that one was used. |
client_id |
The client. |
credit_note_id, credit_note_o_id_full |
The credit note, such as CN1031. |
credit_note_reference |
Its Reference. |
credit_note_total |
Its total, tax included. |
credit |
What became the client's credit. Empty when an existing credit note was used. |
run_text says "Successfully created credit note." or "Found the existing credit note with Reference …".
Send Statement¶
Send Statement emails a client their statement as a PDF.
| Setting | What to enter |
|---|---|
| Client ID | Required. |
| Statement | What is owed now (an outstanding statement, aged by how overdue) or Everything between two dates (an activity statement with a running balance). |
| From, To | For Everything between two dates. Blank From: the 1st of this month; blank To: today. |
| Send to (optional) | An email address. Blank: the client's first contact with an email address. |
It's sent from the person responsible for the client. The task stops if the client has no person responsible, or no contact with an email address and none is given.
Outputs: client_id, statement_type, statement_sent_to, statement_url (the PDF) and statement_balance
(what it says is owed). run_text says "Sent the statement."
To send every client who owes you their statement each month, see Monthly statements.
Post Journal¶
Post Journal posts a manual journal. Your books must be on.
| Setting | What to enter | Example |
|---|---|---|
| Date | Blank: today. | 2026-10-31 |
| What it is for | Required: the journal's narration. | October wages |
| Reference (optional) | Printed after the narration. | PAY-10 |
| Accounts | One account code (or exact name) per line, separated by \|. At least two. |
6200\|2100 |
| Debits, Credits | One entry per line. Leave the other side empty on each line. They must add up to the same. | 4500\| and \|4500 |
| Line descriptions (optional) | One per line. | Wages\|Wages owed |
Running it again with the same date, narration, Reference and lines posts nothing new: was_created is false and
run_text says "This journal was already posted, so it was not posted again." A date in a locked period, an archived
account or lines that don't balance stop the run.
Outputs: was_created, journal_id, journal_number, journal_date.
Record Money Spent / Received¶
Record Money Spent / Received records money spent or received through a bank account in your books, such as a bank fee or a cash sale. Your books must be on.
| Setting | What to enter | Example |
|---|---|---|
| Money in or out | Money spent or Money received. | Money spent |
| Bank account | Its name or its account code. | Business Checking |
| Date | Blank: today. A date after today is refused. | – |
| Client ID (optional) | The client the money came from or went to. | – |
| What it is for, Reference (optional) | The description and the bank's reference. | Bank fee, FEE-1102 |
| Prices are | Whether the amounts include tax. | Tax inclusive |
| Accounts | One account code per line. | 6100\|6200 |
| Amounts | One per line. | 25.00\|100.00 |
| Tax rates (optional) | Each line's tax rate by name or percentage. Blank: no tax. | Sales Tax\| |
| Line descriptions (optional) | One per line. | – |
With a Reference, running it again finds the one already recorded on that bank account and date: was_created is
false. Match the bank line to it in bank reconciliation when it
shows on your statement.
Outputs: was_created, bank_transaction_id, bank_transaction_total, bank_transaction_tax.
Workflows run as BaseCloud's system user, so they don't need the books rights a person does.
Bringing old documents over¶
Moving to BaseCloud from QuickBooks, Xero, Sage or a spreadsheet? This task brings your old quotes, invoices, credit notes and payments over, each with its own date. The whole checklist, from picking your books' start date to proving your balances, is in Moving to BaseCloud from another accounting system. In short:
- Create Invoice (and Create Quote, for old quotes) with Date set to the old document's date, Reference set to its old number, Expected total set to its old total, and Tax amount set to its old tax, so a rounding or tax-rate difference stops the run instead of slipping through. Set Prices are to match the old system. To keep the old numbers themselves, set Next number in Settings first.
- Create Credit Note for old credit notes, and for a client's unused credit (a credit note on its own).
- Mark Quote / Invoice Paid for each old payment, found by Or find it by its Reference with the Client ID, with its Date paid, its Amount when it paid part of the invoice, and its payment Reference. Without the payments, an old invoice opens as still owed.
Running it again is safe. With If the client already has this Reference on Use that document, a document
the client already has is used, not made again, and was_created is false. A payment with a Reference is never
recorded twice: the same Reference, amount and date is found and was_recorded is false. So map the payment's own
reference on every Mark Paid, and let every step run on a re-run: don't skip Mark Paid when was_created is false,
or a payment that failed the first time is never recorded. Choose Create a new one only when a Reference can appear
on more than one document, such as a customer's PO number.
Old documents start no automations. Old document: don't start automations decides whether a document or payment this task records starts your automations: Quote/Invoice Created, Payment received, Marked as paid, a quote turned into an invoice, and Credit note created.
| Choice | Automations start… |
|---|---|
| Automatic: only when dated more than 30 days ago (the default) | For a document or payment dated in the last 30 days, or later. Nothing starts for one dated more than 30 days ago, so a payment your bank feed or Xero brings in a few days late still starts them. |
| Yes, never start them | Never. Use this for an import. |
| No, always start them | Always, whatever the date. |
A note is still written on the client either way. A workflow that records yesterday's payments from your bank, and should still thank the client, needs No, always start them.
Real-world examples¶
Quote a client when an enquiry arrives¶
Form Submission
└─ Match to Client look the client up
└─ BaseCloud Accounting Create Quote
└─ Email attach {{task_<ID>_document_url}}
Thank a client who accepts a quote online¶
CRM Trigger (Quote / Invoice Change: Quote accepted online)
└─ BaseCloud Accounting Fetch Quote / Invoice (the trigger's quote_invoice_o_id_full)
└─ Email thank them, with the payment link {{task_<ID>_payment_link}}
Chase overdue invoices every morning¶
Timer (every weekday, 08:00)
└─ BaseCloud Accounting Get Quotes / Invoices: Days overdue (at least) 7
└─ Loop over quote_invoice_ids
└─ BaseCloud Accounting Fetch Quote / Invoice
└─ Email the reminder, with the payment link
See Overdue invoice reminders and Monthly statements.
Troubleshooting¶
| Message | What to do |
|---|---|
| "No quote/invoice found." | The number or Reference matches nothing. Check it on the Accounting page; use {{task_<ID>_quote_invoice_o_id_full}} from the create step. The workflow carries on. |
| "… isn't paid, so it was not reconciled" / "… is only part paid, so it was not reconciled" | Only an invoice paid in full can be reconciled. Record its payment with Mark Quote / Invoice Paid first, or branch on quote_invoice_payment_status from a Fetch step. |
| "Invoice already marked as paid." | Nothing was owed (paid in full, perhaps by a card payment a moment earlier, or void). Nothing was recorded. Branch on already_paid if the next steps should only run when this step recorded the payment. |
| "… is set to "…", which resolved to nothing." | A setting is mapped to a variable that was empty. Check the step it comes from. |
| "… isn't a date. Use YYYY-MM-DD. Or use DD/MM/YYYY." | Use one of those formats; the Date Formatter task can convert others. |
| "Date paid … is after today" | A payment is recorded on the day it was received. |
| "… isn't an amount more than zero" / "Line n: the unit cost "…" isn't a number" | Map a number. Symbols, separators and % are fine; text isn't. |
| "… has 2 entries, but there are 3 item descriptions" | Give every list one entry per line. |
| "Job date has 4 entries, but there are 3 lines." | A field's answers have more entries than the document has lines. Give one per line, or one answer with no \| for every line. |
| "Line 2: Crew "Delta" isn't one of its options: …" / "PO Total "abc" isn't a number." | A field's answer can't be read. Use one of the options listed, or the form in How answers are read. |
| "… is not on quotes, so it was left out." / "A field this task sets no longer exists, so it was left out." | The run went ahead without that field. Check which documents the field is on in Settings › Quote & Invoice Fields, or remove the setting from the task. |
| "… looks like a number from another system" | Map it to Or find it by its Reference with the Client ID. |
| "More than one document has the number …" / "2 of this client's documents have the Reference …" | Use the other way of finding it. |
| "… is another client's." | The number names another client's invoice. Check the mapping, or use the Reference. |
| "The lines come to …, but the expected total is …" | Rounding, a different tax rate or tax mode. Compare with the old document, set Prices are and Tax amount, and run it again. |
| "… would be dated …, in a locked period" / "The payment date is in a locked period" | With your books on, the date is on or before your lock date. Use a later date. |
| "Your books aren't switched on." | Post Journal and Record Money need your books. |
| Card charged but invoice shows the payment twice | Leave Mark Paid out of card workflows: see the tip under Mark Quote / Invoice Paid. |
| No workflow ran on Marked as paid | The invoice was settled by a write-off or a credit note with no money, or the task's Old document setting said not to. |
FAQ¶
Can I edit a quote or invoice after this task creates it? Its layout, due date and Reference, with Edit Quote / Invoice, while nothing has been paid on it. Its quote and invoice fields, even once it's paid. Edit its lines in the client's Accounting tab.
How do I send the invoice? Follow this task with an Email task that attaches
{{task_<ID>_document_url}} (its Attachments (URL)) and includes {{task_<ID>_payment_link}}. The PDF is made
when the email is sent, so it shows the document as it is then. Or switch on Email each invoice when it's made for
recurring invoices.
How do I bill clients on a schedule? Use Recurring invoices for the same lines every period, or a Timer Trigger and this task for anything else.
What happens when an invoice is paid through its payment link? The payment is recorded for what the client paid, and workflows on Marked as paid and Payment received (CRM Trigger) run, as they do when it is marked paid by hand or by this task.
Discounts? Use Discount(s) % for a percentage off a line, or a line with a negative unit cost for an amount off.
Refunds? Refunds are recorded in the CRM by someone with Refund and remove payments: see Refunds.
Can I bring invoices over from my old accounting system? Yes, with their own dates and old numbers. See Bringing old documents over.
Related tasks¶
- Email: send PDFs, payment links and reminders.
- Loop: act on every document Get Quotes / Invoices finds.
- If Statement: branch on
found,already_paidorwas_created. - Stripe and Paystack: charge a saved card for an invoice.
- CRM Trigger: start a workflow on invoice and payment events.
- Plaid Trigger: record a payment when the money reaches your bank account.
- Timer Trigger: run reminders and statements on a schedule.