[Lunch Flow] How to get the "Remittance Information Structured" aka "purpose" #301
-
|
Not sure if this is a bug or just a knowledge or configurational issue. Is there a way to include those and use them for category rules? Best regards, Boris |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 3 replies
-
|
The Sure app currently does not import or expose the "Remittance Information Structured" (purpose) field from Lunchflow transactions. Only fields like id, accountId, amount, currency, date, merchant, and description are processed and stored, so any remittance or purpose data present in the original Lunchflow payload is ignored by the import logic and not available for category rules or display. This is not a bug or configuration issue, but a limitation of the current implementation. Supporting these fields would require code changes to extend the import pipeline and transaction models to capture and use them for categorization or rules. Details in code To reply, just mention @dosu. How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other |
Beta Was this translation helpful? Give feedback.
-
|
Definitely more of a question than an issue, specially since this is governed by the aggregator (Lunch Flow) and not Sure. I will let @amrawadk answer in detail ... but he has a very cool templating system to extract everything that comes to him, and eventually makes it to us. |
Beta Was this translation helpful? Give feedback.
-
|
Hey @borishinzer 👋 Thanks for checking out Lunch Flow! Since every bank returns data in a slightly different way, and your use may vary, we allow you to configure what you want to include in the 'Merchant' and 'Description' fields of the transaction. If you go to the connections page on Lunch Flow, and click into any of your accounts, you'll see a way to configure those, can you give that a try and let me know if that works for you? 😄 |
Beta Was this translation helpful? Give feedback.

if you switch on the 'advanced' mode, you'll see a couple of examples, one of them uses the
remittanceInformationStructured, does that help?A transaction in Sure has a merchant, and a name, both are acceessible to category rules. I can see that the 'Description' from Lunch Flow would map to Sure's transaction name, and the 'Merchant' in Lunch Flow would map to Sure's transaction merchant.