Reference (partial) — Payment types and engine behaviour are verified from code (September 2026). Your brand’s exact code names, amounts, and eligibility trees live in Admin under SME Payments Settings and are not duplicated here.

Overview

Each payroll row links to a reason code — a general-code record of type SMEPaymentShidduch. The code stores a payment type, default amount, optional eligibility rules, and optional parent code for tiered bonuses.

verified — Reason codes are brand-specific. Ops configure them under Settings → SME Payments Settings (not the same screen as the payroll list). The matchmaker payroll list and dialog read the same active codes.

When automation creates a row, the platform evaluates every active code that matches the milestone’s payment type, checks eligibility, sums nested parent amounts, and saves one Pending row for the highest total. See SME Payments → Automatic payments for when each type fires.

See also: SME Payments · Pre-validation (shared concept) · Matchmaker workflow

Payment types

Every reason code is tagged with exactly one of four payment types. The Type column on payroll rows shows the translated label for this type (your brand may word them differently).

Payment type (internal)Plain meaningWhen automation runsTypical ops use
Second date (date2) Couple reached at least a second recorded date on the shidduch. verified — When status is Dating and the matchmaker records a date number that newly crosses 2 (even if date 1 was skipped earlier). Standard mid-dating milestone bonus.
Third date (date3) Couple reached at least a third recorded date. verified — Newly crosses 3 in the same dating update (jumping from 1 to 4 still pays 2 and 3 if not paid yet). Higher dating milestone.
Fourth date (date4) Couple reached at least a fourth recorded date. verified — Newly crosses 4. Late-dating milestone; some brands stop at three dates.
Engagement (engagement) Couple became engaged through this introduction. verified — When shidduch status becomes Engaged. Leaving Engaged cancels pending engagement rows (paid rows stay for finance review). Largest bonus; often has stricter eligibility rules.

Only these four types exist in the product today. You cannot add a new payment type without an engineering change — create additional reason codes under an existing type instead (for example separate engagement bonuses for different member segments).

Date types map to matchmaker Record date dialog numbers on Shidduch request detail. Engagement maps to Mark Engaged or the engaged outcome on the workflow bar.

Configure reason codes

Open Settings → SME Payments Settings. Requires access to that settings page.

List columns

ColumnWhat to enterEffect on payroll
Name Short label ops recognise (for example “Engagement — in-network”). Shown as Reason on payment rows and in the dropdown.
Pre-Validation (expand row) Click the underlined condition count to open the eligibility editor. Rules automation must pass before this code can create a row. See Eligibility rules.
One of the four payment types above. Groups the code with a milestone; only codes matching the triggered type are considered.
Amount Default amount in brand currency (non-negative number). Base amount before parent codes are added. Auto-fills manual when you pick this code.
Copy / Delete Duplicate a code (useful for variants) or remove it. Inactive/deleted codes no longer appear in dropdowns; existing payment rows keep their historical link.

Add payment setting dialog

Click Payment Setting in the actions bar:

FieldWhat to enterAfter confirm
Name Required display name. Creates a new active code with empty eligibility rules (you can add rules by expanding the row).
Payment type (defaults to second date). Stored on the code; cannot be mixed across types on one row.
Amount Default amount. Used as the code’s own base amount in automation and manual add.
Parent Optional — pick another payment setting code. Builds a nested tree; child amounts include all ancestor amounts. See Parent and child codes.

Inline edits on existing rows auto-save when you change name, payment type, or amount. Eligibility rules save when you confirm changes inside the expanded panel.

Eligibility rules

Each code can require profile conditions before automation pays that code. Uses the same rule builder as questionnaires and groups.

verified — Expand a row’s Pre-Validation cell to edit AND/OR condition groups on member attributes (location, user type, tags, and so on). Full operator reference: Attribute filter conditions and Pre-validation.

Who must pass?

  • Automation — For each candidate code, either the initiator or the responder must satisfy the code’s rules and every parent code’s rules in the chain. You do not need both singles to qualify — one matching member is enough for that code to enter the race.
  • Parent chain — A child code also inherits ancestor rules. If a parent’s conditions fail for both parties, the child cannot win even if its own rules pass.
  • Empty rules — A code with no conditions is eligible for every introduction (still filtered by payment type and active flag).

Manual add does not re-check

on the payroll list lets you pick any active code without running eligibility rules again. Use manual rows for corrections only; rely on automation for policy enforcement.

Re-calculate and skipped pre-validation

When ops run Re-calculate, candidates that fail eligibility are counted in the result as skipped pre-validation — no row is created. Fix the code rules or member attributes, then re-run or add manually.

Parent and child codes

Stack bonuses when a more specific code should pay the base amount plus every parent tier.

verified — When you set a Parent on a code, automation treats the payable amount as:

this code’s amount + each ancestor’s amount (walking up the parent chain until there is no parent).

Example (illustrative amounts)

  • Engagement — base — type engagement, amount 500, no parent.
  • Engagement — premium segment — type engagement, amount 200, parent = base code.

If a couple qualifies for the child code, the row amount is 700 (200 + 500). If only the base rules pass, automation pays 500 from the base code alone.

When several codes of the same payment type pass eligibility, automation picks the one with the highest total (including ancestors), not the first row in the table.

Parent codes may use a different payment type in the database, but only codes matching the triggered milestone type are candidates for that run. Ancestors of any type still contribute their stored amounts when summed.

How automation picks a code

verified — End-to-end flow when a milestone fires (dating date recorded or engagement marked):

  1. Load all active SMEPaymentShidduch codes for the brand.
  2. Keep only codes whose payment type matches the milestone (date2, date3, date4, or engagement).
  3. Drop codes whose eligibility (including parents) fails for both singles.
  4. Compute total amount for each remaining code (self + ancestors).
  5. Select the code with the highest total; create one Pending row linked to that code and the introduction’s assigned matchmaker.
  6. If a non-cancelled row already exists for the same introduction and payment type, return it instead of duplicating (idempotent).

Re-calculate with Override existing pending payments can cancel an existing Pending row for that type and run the calculator again — never overwrites Paid rows.

Milestone timing details: Automatic payments. Engagement cancellation: Engagement broken — ops playbook.

Manual payments

From you choose the reason code directly. Amount defaults from the code but can be overridden. Eligibility trees are not evaluated — ops are responsible for policy compliance.

Use manual rows when automation missed a milestone (after checking Shidduch request logs), when eligibility rules were wrong at the time of the event, or for one-off adjustments. Prefer Re-calculate for bulk backfill from matchmaker activity logs.

Field-level steps: SME Payments → Add payment dialog.

Audit your brand tree

This reference explains engine behaviour — your live code names, amounts, and eligibility rules live only in Admin. Use the checklist below before changing production payroll.

verified — Open Settings → SME Payments Settings on the brand you are configuring. Each row is one reason code. This page does not copy brand-specific amounts because every brand maintains its own tree.

Read the table top to bottom

  1. Group by payment type — Filter mentally (or sort your spreadsheet export) by : second date, third date, fourth date, engagement. Automation never mixes types on one milestone.
  2. Spot parent links — The Parent column (or add-dialog parent picker) shows which code stacks on top of another. Walk from child to parent until the parent is empty — that chain is what automation sums.
  3. Check eligibility — Expand Pre-Validation on each code in the chain. Remember: either initiator or responder can satisfy a code, but every ancestor’s rules must pass for a child to win.
  4. Compare amounts — For each competing code of the same type, add the child amount plus every parent amount. The highest total wins when multiple codes pass — not the first row in the table.

Example audit (illustrative — replace with your brand)

Suppose engagement has three active codes:

  • Engagement — standard — type engagement, amount 400, no parent, no rules.
  • Engagement — in-network — type engagement, amount 150, parent = standard, rules require in-network user type.
  • Engagement — premium — type engagement, amount 250, parent = standard, rules require premium plan attribute.

A couple that qualifies only for standard receives 400. A couple that qualifies for in-network receives 550 (150 + 400). If both in-network and premium pass, automation pays 650 vs 550 — premium wins because 650 is higher.

Test before you rely on a new code

StepWhat to do
1. Save the code Confirm the row is active and the payment type matches the milestone you expect (date 2 vs engagement).
2. Pick a test introduction Use an internal test pair on Shidduch requests at the right stage (dating date recorded or engaged).
3. Re-calculate On SME Payments, run Re-calculate for the payment month. Check whether the result mentions skipped pre-validation — that means no code’s rules matched both singles.
4. Read the payroll row Open the new Pending row: Reason should be the winning code name; Amount should equal that code’s base plus all parents. The same rows appear on Shidduch detail under Payroll when the feature is on.

When two ops disagree on the amount

  • Confirm which code name is on the payment row — that is the automation winner, not necessarily the code you expected from the table sort order.
  • Re-open eligibility on the winning code and each parent — a parent failure removes the child from the race even when the child’s own rules look correct.
  • For manual corrections, use only after you understand why automation skipped or picked a different code — manual rows bypass eligibility.

Export tip: use General Codes filtered to type SMEPaymentShidduch if you need a spreadsheet snapshot for finance review — still treat Admin as the source of truth for live amounts.