SumWise · Synthetic sample deliverable

Sample Workflow Calculation Review

Payment Settlement Reconciliation

Synthetic example — no client or production data

One financially important rule. Explicit assumptions. A defined failure boundary. Expected outputs your workflow owner can check before trusting the rule in production.

This representative sample shows the structure of SumWise's one-time $99 Workflow Calculation Review for one supported calculation rule. It is separate from paid Compute API access unless access is explicitly arranged.

Have one calculation you want to harden? Send the rule or formula first. Avery will confirm whether it fits SumWise before you purchase the $99 review.

01 The business rule

A payment processor deposits a net settlement after refunds, processing fees and chargebacks. Flag the settlement for review when the actual bank deposit differs from the expected net by more than $0.05.

1. Calculate expected net settlement.
2. Subtract expected net from the actual bank deposit to get signed variance.
3. Take the absolute value.
4. MATCH when absolute variance is at most 5 cents.
5. NEEDS REVIEW when absolute variance is more than 5 cents.

Specification & integration

02 Integer cents, one currency

Convert all money to integer cents before calculation. This avoids unnecessary decimal/binary floating-point behavior in the reconciliation rule. All values in one calculation must represent the same currency.

Calculation specification

expected_net_cents = gross_sales_cents - refunds_cents
                     - processing_fees_cents - chargebacks_cents
variance_cents = actual_deposit_cents - expected_net_cents
absolute_variance_cents = abs(variance_cents)

MATCH        when absolute_variance_cents <= tolerance_cents
NEEDS REVIEW when absolute_variance_cents > tolerance_cents

SumWise Compute integration pattern

The current public API is Evaluate-only: POST /v1/evaluate. Build a fixed expression from validated integers. Braces below are documentation placeholders, not SumWise expression syntax.

abs({actual_deposit_cents} - ({gross_sales_cents}
    - {refunds_cents} - {processing_fees_cents} - {chargebacks_cents}))

Concrete first synthetic request:

{"expression":"abs(1034250 - (1075000 - 25000 - 12750 - 3000))"}

Expected numerical result: 0. With validated integer inputs:

result.type      = integer
result.exactness = exact
result.value     = "0"

Compute returns the exact absolute numerical variance. The customer's workflow IF/branch step decides absolute_variance_cents <= tolerance_cents; the API does not perform that business branch. Validate and interpret the returned string as an integer before comparison; do not compare numeric strings lexicographically or lose integer precision.

See the current API documentation for authentication, response shape and limits.

Expected outputs · cases 01–06

03 Check both sides of the boundary

All ten cases use tolerance_cents = 5. Amounts below are dollar-formatted for reading; calculations use integer cents. Signed variance is actual minus expected. The decision uses absolute variance.

Expected outputs · cases 07–10

Zero activity, mixed deductions & larger amounts

The tolerance remains 5 cents, including the zero-activity case. All money inputs in that case are zero. Full inputs are shown for every test.

Failure boundary & workflow handoff

04 Invalid is never a match

Missing required amount

Do not evaluate. Route to input error / review; missing values must never silently become zero.

Negative refund

Reject under this business contract.

Non-integer cents

Reject or normalize explicitly upstream. Never silently round fractional cents.

Deductions exceed gross

Reject under this sample unless the business explicitly allows negative settlements.

Mixed currencies

Reject. Currency conversion is outside this rule.

Edge conditions to preserve

• Preserve signed variance until the final abs() operation.
• <= 5 is intentional. Replacing it with < 5 changes the rule.
• API or transport failure must never become a MATCH.
• With validated integer-cent inputs, an unexpected approximate result is an integration/contract problem, not a successful reconciliation.

n8n implementation note

1. Input / source system
2. Validate required fields and convert money to integer cents
3. Build the fixed SumWise expression from validated integers
4. SumWise Compute / POST /v1/evaluate
5. Validate HTTP/result shape and exact integer result
6. IF absolute_variance_cents <= tolerance_cents
   True → MATCHFalse → NEEDS REVIEW

A failure at validation or the service step takes the error/review path, never the MATCH branch. Store the issued API key in your integration's credential facility. Never put a key in expression text, workflow logs, screenshots or browser/client-side code.

Review scope & fit

05 What the review is designed to catch

• Reversed variance sign
• Forgotten deduction
• < versus <= boundary mistakes
• Dollars/cents mixups
• Unnecessary decimal floating-point behavior
• Missing values becoming zero
• Malformed inputs
• Calculation-service failure treated as successful reconciliation
• The same rule implemented differently across workflows

For this absolute-variance decision, reversing the sign alone does not change MATCH versus NEEDS REVIEW. Recording signed variance still exposes the reversal and keeps reporting and later rules consistent.

For one supported rule, the $99 review can provide

• Written calculation specification, assumptions and input contract
• Edge and failure conditions
• 8–12+ synthetic test cases with expected outputs
• A short n8n / Make / HTTP integration note where relevant
• An explicit in-scope / out-of-scope statement
• A fit check before purchase

Scope of this sample

This is a synthetic sample deliverable, not a paid-client case study, testimonial or evidence of an engagement. A real review is scoped to your supported rule after a no-data fit check. It is not a security/compliance certification or a guarantee of ROI or production suitability.

The $99 Workflow Calculation Review is a one-time service. Hosted Compute private-alpha/API access is separate unless included under separate agreed terms. Currency conversion, production system access and broader custom engineering are outside this sample's scope.