Overview

tracks compensation owed to matchmakers (SMEs) for shidduch work. Each payment row links to one introduction (Shidduch id) so finance and ops can trace which milestone triggered the amount.

Go to → . The whole area is available only when your brand enables the Show SME Payments app feature — without it, the menu item and the Payroll card on Shidduch request detail stay hidden.

Most rows are created automatically when a shidduch reaches dating or engagement milestones (see Automatic payments). Admins can also add manual rows, re-scan matchmaker logs for a month, export payroll CSV, mark batches as paid, and email matchmakers a summary table.

Payment list columns

verified — Singles are shown as female / male columns (derived from each profile’s gender), not as initiator/responder. Location labels come from each member’s stored location attribute.

ColumnMeaningNotes
TypeHigh-level category from the payment-reason code (for example second-date milestone vs engagement bonus).Uses the configured payment reason type on the general code, not the free-text reason name alone.
MatchmakerWhich SME receives this payment.When Multi MMS is on and two or more matchmakers are assigned to the shidduch, the cell lists every assigned name separated by semicolons (or 2+ MM assigned when names have not loaded yet).
MatchesIntroduction number — click to open that row on Shidduch requests.Same id as on Admin Matches.
FemalesName of the woman in the pair (click opens her end-user profile).—
Female LocationHer location label as stored on the profile.—
MalesName of the man in the pair.—
Male LocationHis location label.—
AmountPayment amount in your brand’s currency.On multi-matchmaker shidduchim, one row may represent the full amount before split at payout time — see Multiple matchmakers.
ReasonHuman label from the linked general code (configured under General Codes, type SMEPaymentShidduch).Each code can carry a default amount and eligibility rules.
StatusPending, Paid, or Cancelled — see Payment statuses.Colour chip on the row.
CreatedWhen the payment record was first saved.—
UpdatedWhen the row last changed (status, amount, comment). filter uses this date — not Created.

Filters

FilterWhat it does
Calendar month on the payment’s Updated date. Defaults to recent months in the dropdown; leave empty to load all dates.
MatchmakerShow only rows where that SME is the stored payee (mmId on the row).
StatusPending, Paid, or Cancelled.

Changing a filter reloads both the table and the stats bar totals for the same scope.

Stats bar

StatMeaning
Sum of Amount on rows with status Pending in the current filter.
Sum on Paid rows in the current filter.
Sum of all amounts in the filter (includes Cancelled rows — they still appear in the total).

Who can use this area

PermissionList pagePayment detail
Access on SME Payments (page 9.18)View list, filters, stats, export CSV, re-calculate.—
Add New dialog.—
EditBulk , Send Email, re-calculate with override.Change status, edit comment, Save.
Delete—Remove a payment row after confirmation.
View payment detail (page 9.19)Click any row to open it.Full record.

Matchmakers do not use this Admin list for payroll — their own payment history lives in the matchmaker app when enabled. Admin visibility is intentionally separate from matchmaker self-service.

List actions

ActionWhat it doesPermission
ExportDownloads a CSV of the currently filtered rows. Dual-matchmaker payments split into one CSV line per responsible matchmaker with an even share of the amount. Sorted by matchmaker last name.Access
Re-calculateOpens the re-calculate dialog — scans matchmaker activity logs for the chosen month and creates missing payment rows. See Re-calculate payments.Edit
Manual payment for one shidduch. See Add payment dialog.Add New
Marks every selected row as Paid. See Marking payments as paid.Edit
Send EmailEmails each selected matchmaker one summary message with an HTML table of the chosen rows. See Send payment summary email.Edit

Row checkboxes accept any status — you can select already-Paid rows when re-sending a summary email. Bulk on an already-paid row is harmless (no duplicate payout email).

Add payment dialog

Manual backfill when automation missed a milestone or ops need an exceptional payment.

FieldWhat to enterAfter confirm
Matches Numeric introduction id, then click Search. Loads the shidduch and assigned matchmaker(s). Fails when the id does not exist or no matchmaker is assigned (No MM Assigned).
Reason Pick one active SMEPaymentShidduch general code. Dropdown shows payment type + code name. When the code stores a default amount, Amount auto-fills (you may override).
Amount Positive number in brand currency. Stored on the new row.
Matchmaker Shown only when two or more SMEs are assigned — pick exactly one payee for this row. Hidden when only one matchmaker is on the shidduch (that person is selected automatically).
Comment Optional internal note (multiline). Saved on the payment; visible on the detail page.

creates the row in Pending status. Configure reason codes under Settings → SME Payments Settings (see Payment reason codes → Configure). Automated creation uses the same codes plus eligibility rules — manual add does not re-run those rules.

Re-calculate payments

Ops tool to rebuild missing payroll rows from matchmaker log activity in a calendar month.

verified — Opens from Re-calculate. Pre-selects the same month as the list’s filter when set.

FieldWhat to pickEffect
Month to scan (required). Finds shidduch milestones logged in that month that should have triggered a payment.
Override existing pending payments (checkbox) Off (default) — insert only rows that do not exist yet for each payment type. On — replaces existing Pending rows for the same payment type by cancelling the old row and creating a fresh one. Paid rows are never overridden (those shidduch/type pairs are skipped).

After confirm, a success toast reports how many candidates were found, how many rows were created, skipped because they already existed, skipped because already paid, or failed. Use when matchmakers report missing date-milestone payments after late data entry on Shidduch requests.

Automatic payments

Most rows are created without using .

verified — When a shidduch status changes on the matchmaker pipeline, the platform may call the payment calculator for that introduction. It picks the highest-value eligible SMEPaymentShidduch code whose pre-validation rules pass for both singles, sums ancestor code amounts when codes are nested, and saves one Pending row. Duplicate requests for the same payment type return the existing row (idempotent).

Shidduch milestonePayment type triggeredNotes
EngagedEngagement bonus (engagement type)Fires when status becomes Engaged.
Dating — date #2 recordedSecond-date milestone (date2)When the matchmaker records date numbers on Dating, every threshold newly crossed in one update is paid — even if earlier dates were skipped (for example jumping from date 1 to date 4 still pays date 2, 3, and 4 milestones).
Dating — date #3 recordedThird-date milestone (date3)
Dating — date #4 recordedFourth-date milestone (date4)
Engagement broken (introduction leaves Engaged)Cancels pending engagement paymentsAlready-Paid engagement rows are left unchanged for finance review. Pending engagement rows become Cancelled with an auto comment.

Exact amounts and eligibility depend on each brand’s reason codes (pre-validation conditions, default amounts, parent/child trees). Configure codes under Settings → SME Payments Settings; full type catalog and eligibility semantics: Payment reason codes (reference). View rows for one shidduch on the Payroll card — Shidduch request detail → Payroll.

Payment statuses

StatusMeaningTypical next step
PendingOwed to the matchmaker but not yet marked paid in Admin.Included in ; selectable for bulk .
PaidFinance confirmed payout.Counts toward ; matchmaker may receive a paid notification email when status first changes to Paid.
CancelledRow voided — for example engagement reversed, or re-calculate override replaced an old pending row.Stays visible for audit; usually excluded from active payroll workflows.

Marking payments as paid

  1. Optionally filter to Pending and a month.
  2. Select rows with the checkboxes.
  3. Click .

What happens: Each selected row’s status becomes Paid. For rows that were not already paid, the platform sends a matchmaker notification email with the total amount — when two or more SMEs share one shidduch, the email amount is each person’s even share of the row amount (without creating separate payment records). Change a single row from the payment detail page status control instead when you need a comment or one-off correction.

Send payment summary email

Select one or more rows (any status), then click Send Email. The platform groups rows by matchmaker and sends one email per matchmaker with an HTML table listing the singles, amounts, and shidduch ids in that selection — useful after marking items paid or when resending documentation. Dual-matchmaker rows appear split per responsible SME in the table, same as CSV export.

This is separate from the automatic “paid” notification: summary email can include already-Paid history rows for record-keeping.

Export CSV

Export downloads payroll for the current filters. Filename includes the selected payment-cycle month when set (for example sme-payments-2026-09.csv). Columns include matchmaker name, amounts, female/male names and locations, reason labels, and status — formatted for finance spreadsheets.

Payment detail page

Click any list row to open payment #N.

AreaWhat you can do
Header chips Matches (link to Shidduch detail), Created, Updated.
Status control Pick Pending, Paid, or Cancelled. Saving triggers the same paid notification rules as bulk when moving to Paid.
Read-only amount, reason name, payment type band, editable Comment.
Matchmakers table When Multi MMS assigns several SMEs to the shidduch, shows each person’s contact info and an Amount to Pay column with an even split of the row total (display-only — the stored row still has one amount field).
Delete Permanently removes the row (Delete permission).

Multiple matchmakers on one shidduch

When Multi MMS assigns two or more SMEs to the same introduction:

  • The list may show all names in the Matchmaker column, but each payment row still stores one primary mmId (usually from manual add or automation).
  • CSV export and summary email split the row amount evenly across every responsible matchmaker on that shidduch.
  • Marking the row Paid sends each responsible matchmaker their share amount in the paid notification.
  • Manual requires you to pick which SME receives that specific row when several are assigned.