How to Generate Custom Invoice Numbers in Airtable

Q: Can I start numbering from a specific number?

Yes. Set the start number to whatever value you want. If you are migrating from another system where invoices ended at 5,280, set the start number to 5,281 and existing records will not be overwritten (if "skip existing" is enabled).

Every business that tracks invoices, orders, tickets, or cases in Airtable eventually runs into the same problem: you need a human-readable, sequentially formatted ID for each record, and Airtable's built-in options do not produce what you need.

Airtable has an Auto Number field type. It assigns an incrementing integer to each record -- 1, 2, 3, 4. You cannot customize the format, add prefixes, control zero-padding, or reset the counter. If you delete record #3, that number is gone forever. If you need invoice numbers like INV-2026-0042 or ticket IDs like TKT-00157, the Auto Number field cannot help.

Formula fields can add a prefix to the Auto Number ("INV-" & {Auto Number}), but this creates a computed value that changes if the underlying Auto Number changes, cannot be independently controlled, and has no reset capability.

Filla's Unique ID Generator solves this by generating properly formatted, sequential IDs with configurable prefixes, zero-padding, and counter reset options -- written directly to a text field in your Airtable table.

Need formatted IDs in Airtable Filla's Unique ID Generator creates sequential IDs like INV-2026-0042 with configurable format, padding, and reset options

Start free

Why Airtable's Auto Number is not enough

The Auto Number field works for internal row counting, but it fails for business-facing identifiers for several reasons:

No formatting. Auto Number produces bare integers. Business documents need formatted IDs with prefixes, separators, and consistent digit lengths. An invoice numbered "7" looks unprofessional; "INV-0007" does not.

No zero-padding. Record 1 displays as "1" while record 1000 displays as "1000." This creates inconsistent ID lengths that cause sorting problems and look inconsistent on printed documents.

No reset capability. Many businesses reset their numbering annually or monthly. Invoice number INV-2026-0001 starts fresh each year. Auto Number has no reset mechanism.

Deletion gaps. When you delete a record, its Auto Number value is permanently skipped. In some contexts -- particularly invoicing in jurisdictions that require sequential numbering -- gaps are not acceptable.

No prefix or suffix. You cannot make Auto Number produce anything other than a plain integer. Adding a prefix requires a separate formula field, which is computed (not a stored value) and cannot be used in all contexts.

Step-by-step: Generate custom IDs in Airtable

Step 1: Create the output field

In your Airtable table, create a Single Line Text field where the generated IDs will be stored. Name it something appropriate -- "Invoice Number," "Order ID," "Ticket Number," or whatever fits your use case.

This must be a Single Line Text field, not a Number or Auto Number field. The formatted ID (like "INV-2026-0042") contains text characters that only a text field can store.

Step 2: Create a Unique ID Generator tool in Filla

In your Filla workspace, open the base containing your table. Create a new processor tool and select Unique ID Generator. Name it descriptively -- "Invoice Numbering" or "Order ID Generator."

Step 3: Select the source table and output field

Choose your source table and the output field (the Single Line Text field you created in Step 1).

Step 4: Configure the counter settings

This is where you define how your IDs are generated:

Counter scope determines when the counter resets:

Never reset: The counter increments indefinitely. Record 1 gets 1, record 1000 gets 1000, regardless of date.
Reset each year: The counter resets to the start number on January 1. Useful for annual invoicing (INV-2026-0001 starts fresh each year).
Reset each month: The counter resets on the first of each month. Useful for high-volume operations where monthly numbering keeps IDs shorter.

Start number sets the first number after a reset (default: 1). If you want your first invoice to be INV-0100 rather than INV-0001, set the start number to 100.

Zero padding controls the minimum number of digits. Setting this to 4 means the number portion is always at least 4 digits: 0001, 0002, ... 0099, 0100. The range is 1 to 8 digits. Choose a padding length that accommodates your expected volume without excessive leading zeros.

Step 5: Configure handling

Enable skip records that already have an ID to avoid overwriting existing values. This is essential for incremental use -- run the tool whenever new records are added, and it will only generate IDs for records that do not have one yet.

Step 6: Preview and run

Filla shows an interactive preview of the IDs that will be generated. Review the preview to confirm the format and numbering are correct, then click Run.

The tool processes records in the background, assigning sequential IDs to each record that needs one.

Common ID formats and how to achieve them

Here are practical ID format examples and the configuration needed for each:

Invoice numbers: INV-2026-0042

Output field: "Invoice Number" (Single Line Text)
Counter scope: Reset each year
Start number: 1
Zero padding: 4
Note: The "INV-2026-" prefix would need to be part of the ID format. Currently, the Unique ID Generator produces the numeric portion. You can combine it with a formula field for the full formatted ID, or use the generated number as-is if the numeric portion is sufficient.

Order IDs: ORD-00157

Counter scope: Never reset
Start number: 1
Zero padding: 5
This produces sequential numbers 00001, 00002, etc. across your entire table.

Monthly ticket numbers: 001, 002, ...

Counter scope: Reset each month
Start number: 1
Zero padding: 3
Each month starts fresh at 001.

High-volume sequential: 000001 through 999999

Counter scope: Never reset
Start number: 1
Zero padding: 6
Accommodates up to 999,999 records before exceeding the padding length.

Using generated IDs in workflows

Once your records have properly formatted IDs, they become useful across multiple workflows:

Document generation. Reference the ID in Filla's Document Generator templates. Invoice templates, order confirmations, and receipts all need a visible document number. The generated ID field can be inserted as a variable in your document template.

Form pre-fills. When sharing record edit forms with clients or team members, the ID appears as a read-only field that identifies which record is being viewed.

Search and reference. Formatted IDs are easier to communicate verbally and in writing than raw Airtable record IDs. "Can you check invoice INV-0042?" is more practical than "Can you check rec123abc456?"

External systems. When syncing Airtable data to external tools, accounting systems, or client-facing portals, properly formatted IDs maintain consistency and professionalism.

QR codes and barcodes. Use the generated ID as the source value for Filla's QR/Barcode Generator to create scannable codes linked to each record.

Best practices for ID generation

Choose padding length based on expected volume. If you expect hundreds of records, 3-digit padding is fine. If you expect tens of thousands, use 5 or 6 digits. It is easier to start with more padding than to change the format later.

Use "skip existing" for incremental runs. Enable "skip records that already have an ID" and run the tool whenever new records are added. This ensures existing IDs are never changed while new records get the next sequential number.

Do not delete the output field values. The Unique ID Generator tracks the current counter position. If you delete generated IDs and re-run the tool, the counter continues from where it left off -- it does not re-assign old numbers. This maintains sequential integrity.

Consider the counter scope carefully. Annual resets are natural for fiscal-year-based numbering. Monthly resets keep numbers short for high-volume operations. "Never reset" is the simplest and works when you want a single unbroken sequence across all time.

Store IDs in text fields, not number fields. Even if your IDs are purely numeric (like 00042), store them in a Single Line Text field to preserve leading zeros. A number field would strip them.

FAQ

Can I customize the prefix (like "INV-" or "ORD-")?

The Unique ID Generator produces the sequential numeric portion of the ID. To add a prefix, you can create an Airtable formula field that concatenates the prefix with the generated number: "INV-" & {Invoice Number}. This gives you full control over the prefix format while Filla handles the sequential numbering.

What happens if I delete a record?

The counter does not reuse deleted record numbers. If records 001, 002, and 003 exist and you delete 002, the next generated ID will be 004. This maintains sequential integrity and prevents ID collisions.

Can I start numbering from a specific number?

Yes. Set the start number to whatever value you want. If you are migrating from another system where invoices ended at 5,280, set the start number to 5,281 and existing records will not be overwritten (if "skip existing" is enabled).

How does the counter handle concurrent runs?

Each run processes records sequentially and tracks the current counter position. Running the tool multiple times will continue from the last assigned number. Avoid running the same tool concurrently on the same table.

Can I generate IDs automatically when new records are created?

The Unique ID Generator is a processor tool that runs manually from the Filla dashboard. For automatic ID assignment on new records, you would run the tool periodically after new records are added. To prevent duplicates at creation time, consider using Filla's form builder with the reject duplicate values validation on your ID field.

Professional IDs for professional workflows

Sequential, formatted identifiers are a basic requirement for any business process that involves documents, orders, or tickets. Airtable's Auto Number field falls short for business-facing use, but Filla's Unique ID Generator fills the gap with configurable counter scopes, zero-padding, and skip-existing logic.

Try the Unique ID Generator → or explore all of Filla's Airtable processor tools.

Ready to build smarter Airtable workflows? Start with Filla's form builder -- forms, processor tools, and document generation, all Airtable-native.