> ## Documentation Index
> Fetch the complete documentation index at: https://docs.dualentry.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Field Character Limits: Reference

> Character limits on standard DualEntry fields, including memos, line descriptions, names, and reference numbers, and what happens when a value is too long.

DualEntry caps the length of text fields on its standard records. Use this reference when you're writing long memos, importing data from another system, or sending records through the API. The limits below are the ones DualEntry enforces when it saves a record. Every field listed is a text field, and each limit is the maximum number of characters, with a minimum where one is shown. For custom field limits, see [Custom Fields](https://docs.dualentry.com/accountants/platform-configuration/custom-fields.md).

## Memo and description fields

Memo and description limits depend on whether the text sits on the record itself or on one of its lines, and on the record type. A memo on the record itself is capped at 512 characters, except on projects and contract change orders, which have no limit. The table below lists the line limits and those exceptions.

| Field | Limit |
| - | - |
| Memo on any record except a project or contract change order, such as a bill, invoice, journal entry, or payment | 512 |
| Line memo on bills, invoices, cash sales, and quotes | 5,000 |
| Expense line description on bills and direct expenses | 5,000 |
| Line memo on journal entries, intercompany journal entries, purchase orders, sales orders, customer credits, vendor credits, and allocation journals | 512 |
| Expense line description on purchase orders | 512 |
| Expense line description on vendor credits | 256 |
| Line description on customer payments, customer deposits, vendor payments, and customer refunds | 512 |
| Memo on fixed assets and amortizable assets | 512 |
| Memo and description on projects, and memo on contract change orders | No limit |

> [!WARNING]
>
> On bills, invoices, cash sales, and direct expenses, the record's **Memo** field accepts up to 5,000 characters in the form, but DualEntry saves no more than 512. A longer memo fails when you save. Keep the record memo within 512 characters, and put longer text in a line memo or description, which allows 5,000 on these record types.

## Names, references, and contact fields

Names and identifiers have both a maximum and, for most, a minimum length. The limits below apply in the app and through the API unless the table says otherwise.

| Field | Limit |
| - | - |
| Customer name | 1 to 128 |
| Vendor name | 2 to 255 |
| Company name | 1 to 128 |
| Item name | Up to 255 in the app, 2 to 256 through the API |
| Item SKU | 1 to 64 |
| Item description | 512 |
| Account name | 2 to 255 in the app, 2 to 256 through the API |
| Account description | 512 |
| Classification and attribute names | 2 to 128 |
| Payment method name | 2 to 128 |
| Payment method description | 256 |
| Reference number on bills, invoices, purchase orders, sales orders, vendor credits, customer credits, journal entries, and bank transfers | 128 |
| Check number | 48 or 64, depending on the record type, and at least 3 on cash sales |
| Customer email and website | 255 |
| Vendor email and website | 128 |
| Address fields, such as street, city, and postal code, on customers, vendors, companies, and records | No limit |
| Custom field name | 2 to 32 |

Record numbers, such as an invoice number, are assigned by DualEntry, so you don't enter them and they have no character limit to plan for.

## What happens when a value is too long

DualEntry rejects a value over its limit instead of shortening it, so nothing is saved until you fix the field. Where you see the error depends on how you enter the record:

* **In the app**: many forms flag a value that's too long before you save, with an error such as `Description must be 5000 characters or less`. Fields the form doesn't check fail when you save, with an error that names the field.
* **Through the API**: the request is rejected, and the error names the field and its maximum length.
* **Through Bulk Import**: a few columns, such as vendor and account names, are checked when you validate the file. They fail with `Column "<name>" — violates max_length: max length <N>.` Other columns, including memos, fail when the row is written, with `A field value is out of range or too long for the database.` See [Bulk Import Errors](https://docs.dualentry.com/accountants/integrations/automation-and-developer-tools/bulk-import-errors.md).

Header memos longer than 512 characters are a common cause of failed bill and invoice rows when you migrate from another system. To clean up a failed import, see [How to Fix a Failed Bulk Import](https://docs.dualentry.com/accountants/integrations/automation-and-developer-tools/fix-a-failed-bulk-import.md).

## Related reading

* [Custom Fields](https://docs.dualentry.com/accountants/platform-configuration/custom-fields.md)
* [Bulk Import Errors](https://docs.dualentry.com/accountants/integrations/automation-and-developer-tools/bulk-import-errors.md)
* [Bill management](https://docs.dualentry.com/accountants/core-financials/accounts-payable/bill-management.md)
* [Invoicing and dunning](https://docs.dualentry.com/accountants/core-financials/accounts-receivable/invoicing-and-dunning.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.