REDA One Help Center
EN
Language
English EN Español ES Português PT Italiano coming soon Français FR Deutsch coming soon العربية coming soon
reda.one ↗
Home / REDA Financials AI / Accounts Receivable / Sales Invoices / Creating a Sales Invoice

Creating a Sales Invoice

When you click New on a Sales Invoice, you won't see the usual Salesforce record screen — REDA replaces it with a purpose-built invoicing form. Everything you need is on one page: the invoice header at the top, the line items in the middle, the running totals on the right, and Cancel / Save Draft / Post buttons at the top. This article walks you through it, explains why it works this way, and shows how much the form fills in for you.

Why a custom form? A standard record screen makes you save the header first, then add lines one by one on a related list — slow, and you can't see the total until the end. REDA's form lets you build the whole invoice — header, lines and live totals — in one place, then save or post in a single click. The same form is reused (with the same look and feel) across all the documents you'll raise.
Getting there. Open the App Launcher (the grid icon at the top-left of any page) → REDA Financials AI → the Sales Invoices tab, then click New. Existing invoices open from the tab's list views or global search.
Access you'll need. Creating, editing, and posting Sales Invoices requires the Accounts Receivable v2 permission set (AR clerks & managers) or Accounting Admin v2 (system administrators). The Accounting Controller v2, Accounts Payable v2, and Read Only v2 sets can view invoices but not create or post them.

The form adapts to your setup

One thing worth knowing up front: the fields you see on the form aren't fixed in code. REDA reads a configurable on-screen field list and renders exactly those fields. That means your administrator can add or remove fields on the invoice — an extra reference, a custom dimension, a project code — without any development, and the form picks them up automatically. So your screen may show a few more fields than the examples here; that's by design.

The New Sales Invoice form in REDA Financials AI. Required fields marked with a red asterisk run across the top: Invoice Type set to Invoice, Entity, Currency, Customer, Invoice Date and Due Date, with an optional Reference. Below them Sales Invoice Name is greyed out and reads that it is assigned automatically on save, beside Property, Opportunity, Contact, Cycle Start Date, Cycle End Date, Opp Invoice, Opp Invoice Batch and a Description box. An Invoice Summary panel on the right shows Subtotal $0.00 and Total $0.00, and the header carries Cancel, Save Draft and a greyed-out Post button. A Line Items section begins underneath with Line 1 and an Income toggle.
This is not the standard Salesforce record screen — REDA replaces it with its own form. Two things to notice before you type anything: the greyed Sales Invoice Name is assigned on save, so you never number an invoice yourself; and Post is greyed out until the invoice has a complete line, which is the form telling you that a draft with nothing on it cannot reach the ledger.

Creating an invoice, step by step

We'll bill a customer for some consulting and a laptop. Notice how little you actually type — most of it fills itself in.

1 · Click New. From the Sales Invoices tab, click New to open the form. (Leave the Type as Invoice for a normal bill-now-pay-later sale.)
2 · Choose the Entity. The company issuing the invoice. Picking it sets the invoice's currency and its default ledger, and supplies the receivables (and other) GL accounts the posting will use. The accounting period isn't taken from the Entity — REDA works it out from the Invoice Date you enter next.
3 · Choose the Customer. As soon as you pick them, REDA pulls in their payment terms (which sets the Due Date = Invoice Date + the terms' days) and applies their tax treatment to the lines. (Only customer-class accounts — Customer or Customer & Vendor — are accepted here.)
4 · Set the Invoice Date (defaults to today) and, if useful, a Reference — typically the customer's purchase-order number, which prints on the invoice.
5 · Add the lines. On each line, pick a Product — that auto-fills the description, the unit price and the revenue GL account — then enter the quantity (and a discount if any). Add as many lines as you need; each new product fills itself in the same way. See Sales Invoice Lines for the detail.
6 · Watch the totals. As you type, the form shows the Subtotal, the Tax (a live preview worked out from the customer and products — it's written to the record when you post), and the Total — so there are no surprises before you commit.
7 · Save or Post. Click Save Draft to keep it as a Draft (editable, no accounting yet), or Post to commit it to the books in one step (see below).

What the form fills in for you

This is the reward for setting up your entities, customers and products well — you pick two or three things and the rest appears:

You choose…The form fills in…
EntityCurrency, default Ledger, the receivables (and other posting) GL accounts
CustomerPayment Term → Due Date, tax treatment
A Product on a lineDescription, Unit Price, Revenue GL account
(automatic)The tax on every line, and all the totals
Filing electronically? Decide about Skip E-Invoicing before you post. If your organisation sends invoices to a tax authority and this particular invoice should not be sent — an internal charge, a test document, something outside the mandate — tick Skip E-Invoicing now, while the invoice is still a draft. The flag is read once, at the moment of posting; ticking it afterwards changes nothing, and a posted invoice cannot be edited. See Electronic invoicing on the Sales Invoice.

Save (Draft) vs Post

The two buttons do very different things — it's worth being clear which you want:

ButtonWhat happensUse when…
Save DraftStores the invoice as a Draft. No accounting entries, no customer balance — you can reopen and edit it freely.It's not finished, or it needs approval/review first.
PostSaves and commits it to the books in one action — the accounting entries are created and the customer now owes the balance.It's complete and ready to be official.
What it takes to post. The Post button stays disabled until the invoice has at least one complete line — a product, a quantity, a unit price and a GL account; its tooltip tells you what's still missing. Approval works differently: it isn't checked by the button. If your organisation requires sign-off, you can still click Post, but REDA refuses it — the document requires approval before posting, and its Approval Status must be Approved or Not Required.

Editing, unposting and voiding

Open a Draft invoice and the same form reopens, ready to change. Drafts have no accounting effect, so you can edit them as freely as you like — change lines, amounts, the date, the customer — and save again.

A Posted invoice is different. It is already part of your official books, with live accounting entries and a balance the customer owes. So rather than letting you quietly overwrite a posted figure, REDA opens it in a protected state and gives you two deliberate choices (or simply close the screen to leave it untouched):

ChoiceWhat it doesUse it when…
Reopen as Draft
(unpost)
Pulls the invoice back to an editable Draft. REDA removes the accounting entries it created at posting (and the related tax records), so the books no longer show the invoice — then hands you the same form to correct. Fix what's wrong and Post again to create fresh, correct entries. The invoice keeps its same number. The invoice has a mistake you want to fix and re-issue — wrong amount, wrong line, wrong date.
Void Cancels the invoice for good. REDA asks you for a reason and a void date, removes the accounting entries, and then locks the record. It stays in the system as a cancelled invoice you can no longer edit — a clean audit trail of something that was raised and then cancelled. The invoice should never have been raised, or is being cancelled outright and not replaced with a corrected version.

The key thing to understand is that both remove the invoice's entries from your books — the difference is what happens next. Reopen as Draft means “let me correct this and re-post it”; Void means “cancel this permanently.” Voiding is covered in full in Voiding a Sales Invoice.

If a payment or credit was already applied. When you reopen a posted invoice that a cash receipt or credit memo has already been applied to, REDA shows you exactly what is attached and asks you to confirm — those applications are removed so the invoice can return to Draft. Voiding is stricter: an invoice with payments or credits still applied cannot be voided at all — REDA asks you to reverse the applications first.
If the books are closed through that date. Each Entity carries an AR Closed Through date — the date up to which its receivables books have been closed. If the invoice's date falls on or before that closed-through date, REDA blocks both reopening and voiding (it tells you the period is “closed through” that date), because the books for that time are locked. To reverse such an invoice, raise a credit memo dated in a period that is still open.

Where to go next

  1. Understanding Sales Invoices — the concepts behind invoices.
  2. Sales Invoice Lines — add and edit invoice lines.
  3. Tax on Sales Invoices — how tax is calculated.
  4. Posting a Sales Invoice — post the invoice to the ledger.
  5. Sales Invoice PDF — generate the customer document.

Frequently asked questions

REDA replaces the standard New/Edit screen for invoices with its own single-page form, so you can build the header, the lines and see the totals all at once and post in one click. It's the same experience across all the documents you raise.

No — they come from the Entity and Customer you pick. You generally only enter the date, the customer, and the line items. That's the whole point of the earlier setup.

Yes — click Save Draft to keep it as a Draft. Drafts have no accounting effect and can be edited as often as you like until you post.

Open it and choose Reopen as Draft. REDA removes the accounting entries it created, returns the invoice to an editable Draft (with the same number), and lets you correct it and Post again. If instead the invoice simply shouldn't exist, choose Void to cancel it permanently.

Both remove the invoice's entries from your books. Reopen as Draft brings it back as an editable Draft so you can correct it and re-post — it's for fixing. Void cancels the invoice for good: it records a reason and date, then locks the record as a cancelled invoice you can't edit — it's for cancelling. You can't edit a posted invoice's numbers in place; you choose one of these two paths.

Not at all — the form renders whatever's in your on-screen field list, which your administrator can tailor. Extra fields (a project code, a custom reference) are expected and fully supported.

Was this article helpful?