Customer invoices and adjustment notes
Choose the customer document and apply eligible credits safely
Use Customer Transactions to record customer invoices, additional charges and credit notes. Use Customer Receipts to record cash, and the application controls to match cash or eligible credits to open document lines. These are different events: a credit note is not a cash refund, and applying a credit does not itself return stock.
This guide is for authorised sales and accounting users in the selected company and permitted locations. Start here to choose the document, then use the linked field references for individual controls. Follow the company's approval and fiscal process before changing a saved or submitted document.
Choose the customer document
| Requirement | RavenLedger route | Main result and caution |
|---|---|---|
| Invoice a service or non-stock charge | Customer Transactions with Transaction Type Invoice | Creates the amount receivable and the applicable revenue/tax accounting. Prepare the approved service/revenue mapping. |
| Invoice goods held in stock | Customer Transactions with Invoice and the eligible inventory item | Requires the permitted stock allocation and separate stock/COGS processing. A sales order alone is not an invoice. |
| Invoice against a sales order | Invoice with the applicable SO Line | Links commercial quantities to the order. Review remaining order quantity and the invoice's own price, tax and allocation. |
| Increase an existing customer's amount due | Customer Debit Note | Ordinary customer debit-note lines are positive, as invoice lines are. Preserve the reason and original-document evidence. |
| Reduce an amount due or record a commercial credit | Customer Credit Note | Ordinary credit-note quantities are negative with a permitted nonnegative price; the document provides credit rather than paying cash. Apply eligible credit separately. |
| Sell a fixed asset | Supported asset-disposal/customer transaction route | Use the actual disposal event and its asset accounting. Do not use a normal revenue line to bypass the disposal controls. |
| Counter sale or return | POS checkout and its supported return process | Use POS tender, original-ticket and session controls, not a second customer invoice for the same sale. |
| Record an internal system adjustment | System-generated FX or withholding transaction | Do not manually recreate or edit protected system transactions to force settlement. |
The customer Debit Note increases receivables. Do not copy the vendor note convention: in this release, ordinary vendor Debit Notes and Credit Notes both reduce payables. Use the vendor document guide for that distinction.
Prepare the company customer and tax design
Confirm the company, location, open dates, customer status, customer currency, credit policy and receivable/revenue accounts. For goods, prepare item/UOM, warehouse/bin and required lot, serial or expiry identities. For tax, review the customer-side resolved tax code and its chargeable and withholding components; the vendor default is separate.
Agree the document currency and the rate into functional currency before entry. A bank's currency is chosen later on the receipt; it need not be the invoice currency where the receipt application supports cross-currency settlement. See tax and currency applications.
Create and check an invoice
- Open Customer Transactions in the intended company and select the new-document action. Choose Invoice, location, Transaction Date, Ledger Date and the correct customer.
- Review customer/address defaults, payment terms, currency and the functional FX rate. Enter the customer's external reference and an understandable description.
- Add the service or eligible item lines. Check quantity, UOM, unit price, permitted discount, tax code and account mapping. Link the actual SO Line only when the invoice belongs to that order.
- For inventory lines, complete the application's allocation controls using the permitted location, warehouse/bin and tracking identities. The allocations must agree with the parent line; do not invent an identity to clear validation.
- Check base, chargeable tax, gross, withholding and net receivable in both displayed currencies. Review invoice and receipt fields and stocked-invoice controls.
- Save once, retain the generated transaction number and reopen the document. Inspect the saved lines, balances, stock processing and linked journal state. Complete the separate authorised fiscal process where applicable.
If the response is uncertain, locate the generated transaction before retrying. A timeout, printable invoice or saved header does not prove that all accounting, inventory or authority processing completed.
Create a customer debit note
Use a Debit Note for an authorised additional customer charge, not as an interchangeable reversal. Identify the original invoice, the reason, amount and tax treatment first. Select Debit Note in Customer Transactions, retain the original-document reference where applicable, and review the positive quantities and permitted price. Discount editing on notes is restricted.
Check the increased customer balance and the note's own revenue/tax accounting after saving. A debit note can be a target for an eligible customer credit application. For Pakistan FBR documents, the correction also requires the applicable original fiscal reference and country controls described below.
Create a customer credit note
- Establish the credit reason: price correction, cancellation or return. Agree the amount and tax treatment against the original document.
- Select Credit Note in Customer Transactions and the same customer. Use the intended location, dates and document currency; do not convert a saved invoice merely by changing its type.
- Review negative quantities, permitted prices, restricted discounts, tax and the original-reference requirements. For returned inventory, use the supported allocation and stock treatment as a separate control.
- Save once and reopen the credit. Check its negative net/open amount and available credit, plus its actual journal and stock outcome where relevant.
- If the credit is to settle an open invoice or debit note, use Apply Credit. If cash must be returned, use the separate supported receipt-refund process and treasury authorisation.
An inventory credit does not replace the physical return/inspection decision. A commercial credit application moves open-item balances; it does not itself receive goods into a warehouse.
Apply customer credit to an open document
Open the saved eligible credit line's Apply Credit controls. Choose the exact target Invoice or Debit Note line for the same company and customer. Standard customer credit applications require the same document currency. Review the target's open amount and the source credit still available before entering a positive application amount.
| Control or display | What it means | Check before applying |
|---|---|---|
| Target type number and line | The invoice/debit line being reduced | Match the original business evidence; do not choose by amount alone. |
| Applied Amount | Amount reducing the target, in target currency | Must not exceed that line's open amount. |
| Credit Applied Amount | Credit consumed, in credit-note currency | For the supported same-currency route, it equals Applied Amount and must fit available credit. |
| Cross Currency Rate | Relationship between source and target amounts | Same-currency customer credit applications use 1. The presence of this field is not permission for different-currency targets. |
| Functional Applied Amount | Target amount at its document's functional FX basis | It can differ from the credit's functional value even when both documents are USD. |
| Transaction Date and Ledger Date | Application and accounting dates | Cannot precede the applicable source/target dates; the ledger period must permit the action. |
| Application journal and FX information | Accounting linked to this application | Inspect actual processing; do not substitute the invoice header's journal for the application journal. |
Apply once, reopen the applications and compare both documents' remaining balances. For example, applying USD100 credit to a USD1,000 invoice leaves invoice USD900 and source credit zero if the credit was exactly USD100 and there are no other settlements.
Understand foreign currency credit restrictions
A USD credit against a USD invoice is a same-currency application even if the company's functional currency is PKR. If their document rates differ, a functional exchange difference may still arise. Cross rate 1 does not mean there is no FX accounting.
A EUR credit against a USD invoice is different: the standard customer credit endpoint rejects the currency mismatch in this release. Do not change the saved currency, manipulate an API, invent a cash receipt or post a balancing journal merely to force the application. Ask the accounting owner to choose an approved, supported correction route. Cross-currency cash settlement is explained separately in receipt and payment applications.
Record cash and apply the receipt separately
Save the receipt against the actual customer and bank, in that bank's currency. Confirm amount, dates and the receipt's functional FX rate. A saved receipt initially has an unapplied balance; it does not automatically settle an invoice.
Use the eligible receipt's Select Transaction Line and application controls to identify the intended open invoice/debit line. Review Net Cash Applied, Receipt Applied Amount, currencies, dates and any settlement withholding. Apply once and check the invoice residual, receipt residual, protected withholding records and application/FX journals. Read the worked tax and currency cases before a taxed or foreign-currency application.
Correct or unapply without duplicating the transaction
| Situation | Safe route | What does not happen automatically |
|---|---|---|
| Unsaved entry is wrong | Correct the form before Save | Cancelling an unsaved form does not reverse another saved document. |
| Saved document has no applications and remains editable | Use its authorised edit controls after reviewing processing/fiscal status | Editing a description is not a financial reversal. |
| Credit already has saved applications | Review the supported application correction/unapply action first | Do not commercially edit an applied credit as though it were unused. |
| Wrong ordinary credit application | Use its supported edit/remove action where dates, locks and fiscal state permit; reopen both documents | Removing an application does not cancel the credit note or refund cash. |
| Wrong receipt application | Correct/unapply the originating receipt application where permitted | Protected system withholding allocations are not manually deleted. |
| FBR source is protected after submission | Use the authorised fiscal correction process | Copy, deletion, changed references and manual journals do not undo authority submission. |
| Cash must be returned | Use the supported refund against the original eligible receipt and approved treasury controls | A credit note alone does not transfer money. |
After correction, reconcile the original and resulting records, including zeroed/replacement journals and any remaining stock/tax consequences. Never replay the original import as a correction.
Follow the Pakistan FBR correction controls
Where the company's effective Pakistan FBR profile applies, preserve the original accepted authority invoice reference. Customer credit/debit notes have their own source-reference rules; the accounting note and the electronic correction are not the same event.
For a credit note using accounting applications as its fiscal source, the applicable lines must be fully applied and refer to the permitted single original document. Do not mix manual fiscal references with accounting applications. A reference-only correction uses its supported fiscal-reference controls, not an invented settlement. A Pakistan FBR debit note references its permitted original customer invoice. Submitted credit-note applications and protected source/reference details are locked.
Check the current electronic-invoicing guidance and approved company process before submission. The FBR digital-invoicing provisions are the official starting point for applicable requirements; this guide does not select a statutory rate or replace a jurisdiction-specific decision.
Reconcile the customer trail
Compare the invoice, debit/credit notes, cash receipts, applications and customer statement at the same company/location, date cutoff and currency. Tie the open items to the receivable control after relevant journals are posted. Reconcile chargeable tax and withholding separately; for goods, also reconcile quantities, valuation and COGS.
Use report parameters, GL transaction and close controls and inventory reconciliation. An unapplied receipt or credit can be genuine; investigate it rather than forcing it to zero.
Resolve a blocked customer application
| Message or symptom | What to check |
|---|---|
| Target is missing | Company, customer, type, currency, open balance, existing applications and permitted location. |
| Currency mismatch | Customer notes require the same currency; this is different from a receipt's cross-currency settlement. |
| Amount exceeds available balance | Reopen current target and credit/receipt balances; include earlier applications and settlement withholding. |
| Application date rejected | Compare both linked document dates, ledger dates and the open-period rule. |
| System withholding cannot be removed | Correct the originating receipt application, not its protected child allocation. |
| Saved invoice still appears unpaid | Inspect the actual application and its status, not only the receipt Save result. |
| Journal is missing or processing is uncertain | Inspect the saved transaction and job/journal state before any retry; do not enter a duplicate. |
Continue with fields imports and related tasks
Invoice and receipt fields, stocked sales and credit controls, vendor invoices and notes, tax and currency applications, customer setup, sales bulk imports and POS returns.
Bulk sales and receipt imports for Customers and sales
Use the correct bulk action for this module. The following templates are different business operations, not interchangeable create/update files.
| Action and exact template columns | Prepare the file | Check the saved result |
|---|---|---|
| Sales Orders - Sales Orders | Group order header/Lines with ext_key; prepare customer, location, currency, item/UOM, quantity, price and tax intent. | Match order numbers, line quantities, totals and status. An order is not delivery or invoice recognition. Continue with stocked sales. |
| Customer Transactions - Customer Transactions | Prepare invoice/note type, customer, dates, source relationships and header/line keys. Stocked lines need applicable allocation sheets and matching quantities. | Inspect saved invoice/note, tax, AR, stock/cost and posting/fiscal status. Reconcile using sales transactions; do not replay to correct a posted invoice. |
| Customer Receipts - Customer Receipts | Prepare bank, customer, receipt currency, amount and any supported invoice application data. Distinguish cash, tax/withholding and applied value. | Reconcile bank/cash, customer open items and residual/unapplied amounts. Do not assume every receipt automatically settles invoices. Use receipt guidance. |
| Miscellaneous Receipts - AR Misc Receipts | Prepare cash-receipt category, contra account, bank, dates/currency and traceable references. Do not imitate customer invoice application. | Match receipt amount/sign and cash/contra postings to supporting evidence; use cash and bank. |
Follow this module bulk procedure
- Prepare the customer, receivable/revenue mappings, location, item/UOM and applicable tax/tracking setup. Choose Sales Orders, Customer Transactions, Customer Receipts or Miscellaneous Receipts in its own list.
- Download that action's current template. Keep header and line ext_key relationships intact; for stocked customer transactions, provide the allocation worksheets required for the exact warehouse/bin and lot/serial/expiry state.
- Check customer, dates, currency, quantities, prices, tax/withholding intent and source relationships. For receipts, distinguish cash received, invoice application and unapplied amounts; miscellaneous receipts are not invoice applications.
- Validate the whole intended file and follow the shared commit procedure once. Record the generated order, invoice/note or receipt numbers and inspect their actual saved status.
- Reconcile orders to quantities/totals; invoices to AR, tax, stock/COGS and posting/fiscal state as applicable; receipts to cash, customer open items and remaining unapplied balances. Use the document's supported correction path rather than re-importing it.
Validate, commit and recover safely
For a supported workbook import, use the shared import steps and job recovery. A validated preview is not a saved transaction. Use Show status before retrying; cancelling a job does not reverse committed records. Keep the approved file, job reference and reconciled results securely.
