Have something to say?

Tell us how we could make the product more useful to you.

86c8eurk1 Add Cover Auto-Create Expense Entries from Unmatched Credit Card Statement Transactions

Currently, credit card statements are only used to match existing invoices. We propose extending this functionality to also extract individual transactions directly from the statement and automatically create basic expense entries (date, amount, merchant) for transactions that do not have a matching invoice. This would allow users to automatically include subscriptions, recurring charges, and other automatic payments in their reports without having to manually add them to the Google Sheet report. The feature should: Parse credit card statements as it already does for matching Identify unmatched transactions Create basic expense records (date, amount, merchant name) Clearly mark these entries as “statement-based” or “no invoice attached” This would significantly reduce manual work and ensure more complete financial reporting.

Pavel Yankovskiy 6 days ago

Auto-create and assign tags from extracted invoice fields (e.g., PO number)

It would be very helpful to create automation rules that use extracted invoice data to automatically generate or assign tags. For example, many invoices include a PO number in the document body. The desired workflow would be: Tailride extracts the PO number from the invoice If a tag with that PO number already exists → automatically assign it to the invoice If it doesn’t exist → automatically create a new tag and assign it Currently, PO numbers (and similar custom/extracted fields) are not available as rule inputs, which limits automation possibilities. Enabling rules to reference extracted fields would make invoice organization and filtering much more scalable, especially for high-volume workflows. This feature would allow dynamic tagging based on invoice metadata, reducing manual work and improving consistency.

Pavel Yankovskiy 25 days ago