Custom fields or external references on transactions

[ilias1111]

Describe the feature

Would Sure consider supporting optional custom fields on transactions, or a structured way to attach external reference IDs?

For example, I’d like to store an ID assigned by another system on a transaction, then search or filter by that ID and include it in exports or API responses. Other useful examples might be an invoice reference, an order ID, or a project code.

Today, notes can hold this information, but it’s unstructured: the value is mixed with other text, harder to filter reliably, and awkward for integrations to read or update.

I’m imagining fields that are optional and hidden unless a user chooses to configure them. They could be simple text fields, with the field names defined per household. I’m open to a narrower approach if a general custom-field system would add too much complexity.

Why is this feature important?

Structured references would make it easier to reconcile transactions with external systems and to build reliable exports or automations without encoding machine-readable values in notes.

Additional context, screenshots, and relevant links

I’d be happy to explore implementing this if it fits Sure’s direction. Would maintainers be open to a contribution, and is there a preferred design or scope to consider first?