Branch Name on the e-CF Voucher
How Mosce ERP shows the branch where a sale happened on the e-CF and its Printed Representation, the 20-character limit on the name, why already-issued vouchers never change, and which vouchers fall outside this rule.
The electronic tax voucher and its printed receipt show the branch where the sale took place, taken from the order or invoice itself - not from a single value configured by hand for the whole business. This article explains what you see with one branch, what changes with several, and the limits of this behavior.
Reading time: ~4 min
When to use this
- You have several branches and want to know which branch prints on each invoice or credit note.
- A branch name looks cut off on the voucher and you want to understand why.
- You renamed a branch and need to know whether that affects already-issued invoices.
- You want to know whether this rule also applies to supplier purchases or minor expenses.
Before you start
- This behavior is automatic: there is no setting to turn on.
- It applies to the Fiscal Credit Invoice (E31), the Consumer Invoice (E32), and their related credit notes (E34). What falls outside this is detailed below.
With a single branch, nothing changes
If your business has a single branch, that branch is named the same as the business. The voucher and its Printed Representation look exactly as they always have - nothing new to check.
With several branches, each sale shows its own
As soon as you register more than one branch, every invoice, consumer invoice, or related credit note shows the branch where that specific sale happened, taken from the originating order or invoice. If two branches invoice on the same day, each one prints its own name in the voucher header - never a generic value shared between them.
This information appears in the issuer block, next to the business name, both in the e-CF that is signed and transmitted to DGII and in the Printed Representation you hand to the client.
The name is truncated to 20 characters when needed
The Branch field in DGII's official format has a maximum length of 20 characters. If your branch name is longer than that, Mosce ERP truncates it so it fits within that limit.
This never blocks or rejects the sale: the truncation only affects how that specific field looks on the voucher. The rest of the invoice, its amounts, and its fiscal validity are not affected. If you would rather the full name always show, you can use a shorter name for that branch.
Already-issued vouchers never change
A voucher that has already been signed and sent to DGII keeps forever the branch it carried at that moment, even if you later rename that branch. Renaming a branch only affects vouchers issued after the change; the historical record stays intact, exactly as it was delivered to the client and to DGII.
Sales with no particular branch
If a sale is not tied to any specific branch, the voucher keeps showing the same single value that was used before you had several branches. There is no blank field and no error - it simply keeps the previous behavior.
What falls outside this rule
This rule applies only to the Fiscal Credit Invoice (E31), the Consumer Invoice (E32), and their related credit notes (E34).
Out of scope: vouchers for supplier purchases (E41) and for self-issued minor expenses (E43). These always show the same single value as before, no matter how many branches you have registered.
Common errors
| Symptom | Likely cause | Solution |
|---|---|---|
| The branch name looks cut off on the voucher | The name exceeds the 20 characters allowed by the official format field | This is not a sale error - if you want the full name to show, use a shorter name for that branch |
| An old invoice does not show the branch's new name | The branch was renamed after that voucher was issued | This is expected behavior: already-issued vouchers keep the branch they carried at the moment of signing |
| A sale shows the business name instead of a branch | The sale was not tied to any particular branch | This is not an error - that is how it behaves when there is no specific branch for that sale |
| A supplier purchase invoice does not show a branch | Supplier purchases fall outside this rule | This is expected - purchases always use the same single value as before |
Frequently asked questions
Do I need to configure anything for the voucher to show the right branch?
No. Mosce ERP takes the branch directly from the order or invoice where the sale happened; there is no manual setting to keep up to date.
Does this apply to the Point of Sale?
Yes. A sale collected at the Point of Sale is tied to the branch it was made from, the same as an invoice issued from an order.
Can I rename a branch without losing my invoice history?
Yes. Renaming a branch only changes what prints on future vouchers. Invoices and credit notes already issued keep the name they had at the moment they were signed.
Can the 20-character limit cause DGII to reject my invoice?
No. It is a format limit on the field, not a content validation - Mosce ERP truncates the name before building the voucher, so emission never stops because of this.
Related
Last updated: 2026-09-07
Regulatory sources
- DGII - Formato Comprobante Fiscal Electrónico v1.0 (Issuer block,
<Sucursal>field, page 10): "Indicates the name of the branch that issues the e-CF. It corresponds to data managed by the issuer", with a maximum length of 20 characters (alphanumeric type). Available at the DGII portal. - DGII - Informe Técnico e-CF v1.0 §18.2.1 (Printed Representation header, page 33): the branch is one of the issuer's data points that must appear at the top left of the document header, listed as "Sucursal (si aplica)" ("Branch, if applicable"). Available at the DGII portal.
e-CF Documents
Tray of issued electronic tax vouchers: the ten DGII validation statuses and the distinctions between the ones that get confused, Track ID, amount-range filter, download of the signed XML and the Printed Representation, electronic delivery to the recipient, what happens when DGII rejects a voucher, the E47 Foreign Payment voucher, and credit-invoice requirements.
Minor Expenses
How to record staff minor expenses (consumables, transport, parking, tolls) with no supplier voucher and, once a month, issue a single Minor Expenses voucher (e-CF type 43) that groups them together.