USusesecuro
reconciliation

Accept Suggestion

Changed on

Take the match, and write it the way its kind is written.

An invoice gets an allocation; a recurring bill gets the charge bound to it. The two are genuinely different writes, which is why the suggestion service marks and this route links.

A payment offered against several invoices is accepted whole. The question was "does this cover these three", so answering it two thirds of the way would leave the payment short on the rest with nothing having warned anybody. All the writes happen inside one savepoint: if the last invoice refuses, the first two are not left standing.

post/api/reconciliation/suggestions/{suggestion_id}/accept

Request

Path parameters

suggestion_idstring uuid required

Headers

X-Workspace-Idstring nullable

Response

Successful Response

idstring uuid required
nodestring required
strategy_idstring required
expectation_kindstring required
expectation_idstring uuid required
expectation_labelstring nullable
amountstring required
scoresobject required
statusstring required
created_atstring date-time required

Changes