Credit notes and returns in JoFotara: how return invoices work
The rules for return invoices (credit notes) in Jordan's national e-invoicing system, taken from ISTD's technical integration guide: what they must reference, how partial and repeated returns work, how POS returns fit in, and a worked example to the fils.
Once JoFotara accepts an invoice, it is final. You cannot edit it in your system or on the portal, so every return and every correction goes through a return invoice, which ISTD's technical guide describes as an invoice in the form of a credit note. This guide explains how that document is built and what the national system will and won't accept, based on ISTD's technical guide for API integration (version 1.5, 2026). For the overall setup, from credentials to QR codes, see our JoFotara step-by-step guide; to see credit notes inside an ERP, read about JoFotara e-invoicing integration in Aspirations.
The three rules of a JoFotara return
ISTD's technical guide sets three conditions for any return:
- Returns are on quantities only. You return a quantity of a line that was sold.
- You cannot return more than was sold. The returned quantity of each line cannot exceed its quantity on the original invoice.
- Several returns are allowed. You can send a return against the same original once or several times, until all quantities sold on it are used up.
The first rule has a practical consequence. A return invoice is built around quantities, so a pure price correction (the right quantity at the wrong price) is normally handled by returning the full invoice and issuing a new correct one. Confirm the treatment of unusual cases with your accountant.
What a return invoice must contain
A return uses the same UBL 2.1 invoice structure as a sale, with a few differences that JoFotara checks:
- Its own number and UUID. The return is a new document. Its ID and UUID together form the key that stops it being recorded twice.
- Type code 381. The invoice type code changes to 381 to mark it as a return. The
nameattribute keeps the payment method and invoice kind of the original, so a cash sale is returned as a cash return and a receivables sale as a receivables return. - A reference to the original. A
BillingReferenceblock carries the original invoice's number, its UUID and its total value. The total is the original invoice's total, not the amount being returned. - A reason. The reason for the return is mandatory and goes in the
InstructionNoteelement. - The same buyer. Buyer details on the return must match those on the original sale.
- The same currency as the original invoice.
- Matching lines. Each returned line carries the same line ID, description and unit price as on the original, with the returned quantity.
ISTD's technical guide therefore tells sellers to keep each line's ID from the original sale, because it is used later to match returned items with the original invoice.
Type codes for returns
The name attribute combines where the sale was made (local or export), how it was paid (cash or receivables) and the kind of invoice. The codes for the two common invoice kinds are:
| Return of | Income invoice | General sales tax invoice |
|---|---|---|
| Local cash sale | name="011", value 381 | name="012", value 381 |
| Local receivables sale | name="021", value 381 | name="022", value 381 |
Export returns use their own codes in the guide. Businesses registered for special tax follow a separate template.
Partial returns and discounts
A partial return is the normal case: a customer brings back some of the items. Discounts are the detail that causes rejections. ISTD's guide says that when the full quantity of a line is returned, its full discount goes on the return; when part of the quantity is returned, the discount must be the matching share of that line's discount. Amounts on the return are positive, and the type code tells JoFotara it is a return. Totals follow the same arithmetic as a sale, and the guide allows rounding differences of no more than 0.001.
Worked example
An original cash invoice, registered for sales tax at 16%, has two lines:
| Line | Qty | Unit price | Discount | Net | Tax 16% | Total |
|---|---|---|---|---|---|---|
| 1. Item A | 10 | 5.000 | 2.000 | 48.000 | 7.680 | 55.680 |
| 2. Item B | 2 | 15.000 | 0.000 | 30.000 | 4.800 | 34.800 |
| Invoice total | 78.000 | 12.480 | 90.480 | |||
The customer returns 4 units of item A. Line ID 1, unit price 5.000, quantity 4, gross 20.000. The discount share is 2.000 × 4 ÷ 10 = 0.800, so the net is 19.200, tax 3.072 and the return total 22.272 JOD. In the reference block, the original total is still 90.480. A week later the customer can still return up to 6 more units of A and 2 of B, each time against the same original. To check the tax arithmetic on any figure, use our Jordan sales tax calculator.
Returns at the cash register
A POS sale in Jordan is a cash invoice, so a counter return is a cash return (type 012 for a sales tax registrant) against that receipt. Three points matter in a shop:
- Find the original receipt. The return must reference the original invoice number, UUID and total, so a return without a receipt has nothing to point at. Your POS should let the cashier search by receipt number.
- Return through the same channel. According to the JoFotara portal user guide, the portal can return only invoices that were issued on the portal. Sales your POS sent by integration must be returned by your POS or accounting system.
- Refund from the shift. The cash refund should come out of the current shift so the drawer still matches at closing.
An exchange is two documents: a return for the item brought back and a new sale for the item taken. More on choosing a register in our guide on how to choose a POS in Jordan.
The accounting side
A return reverses the sale for the returned part: revenue, sales tax and, for goods, stock and cost of sales. The General Sales Tax Law (Article 19) lets a registered person credit the tax already charged on returned supplies when accounting for tax, which is why returns appear in your sales tax return. Keep the return linked to the original in your books as well as in JoFotara, so an auditor can follow both.
When a credit note is not the answer
A credit note only applies to an invoice JoFotara has accepted. If an invoice was rejected (status NOT_SUBMITTED with an error), it never became an e-invoice: fix the data named in the error and resubmit it. If it was never delivered because of a timeout or outage, ISTD's technical guide says to resend it with the same ID and UUID rather than create a new one. Issuing a credit note in either case would reverse a sale the national system never recorded.
Common reasons returns are rejected
- Returned quantity above what is left on the original.
- Wrong or missing original UUID, or the return amount entered as the original total.
- Line IDs that don't match the original lines.
- Full discount applied to a partial return.
- Buyer details that differ from the original sale.
- No reason in the return.
- A return sent before the original was accepted.
Credit notes in Aspirations
In Aspirations, a credit note is created from the original invoice, in full or for selected lines. A reason is required, and the original must already be accepted by JoFotara. The credit note references the original invoice number, unique identifier and total, and revenue, tax and stock are reversed automatically. At the POS, the cashier finds the receipt by number and returns all or some lines; the refund is paid from the current shift and you cannot return more than was sold. The integration is ready (UBL 2.1) and requires your own JoFotara credentials. Debit notes, special-tax invoices and export invoices are not supported.
This guide is general information based on ISTD's published technical guide. Requirements can change, so check the current version with the Income and Sales Tax Department.
