From 7e2439f7819b6a6a04541e0dea8986cfc63e6a8b Mon Sep 17 00:00:00 2001 From: Tobias Diez Date: Sun, 18 Aug 2024 22:14:02 +0200 Subject: [PATCH] [WIP] Clarify post-processing in `add/importTransactions` (#438) Clarify that `importTransactions` runs rules --- docs/api/reference.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/api/reference.md b/docs/api/reference.md index aa9ca1c112..d5157f6e38 100644 --- a/docs/api/reference.md +++ b/docs/api/reference.md @@ -183,7 +183,9 @@ This method is mainly for custom importers that want to skip all the automatic s -Adds multiple transactions at once, but goes through the same process as importing a file or downloading transactions from a bank. You probably want to use this one. Returns an array of ids of the newly created transactions. +Adds multiple transactions at once, while going through the same process as importing a file or downloading transactions from a bank. +In particular, all rules are run on the specified transactions before adding them. +Use `addTransactions` instead for adding raw transactions without post-processing. The import will "reconcile" transactions to avoid adding duplicates. Transactions with the same `imported_id` will never be added more than once. Otherwise, the system will match transactions with the same amount and with similar dates and payees and try to avoid duplicates. If not using `imported_id` you should check the results after importing.