Skip to main content

๐Ÿ™…โ€โ™‚๏ธ ๐Ÿ™…โ€โ™€๏ธ Understanding Pending and Rejected Payment Statuses

How Pending and Rejected statuses affect net payment balances and student portal access.

The Issue

Pending and Rejected payments both appear in the Payment Activity section alongside completed payments. Neither status counts toward a student's balance, but without careful filtering, rules and automations may treat them as valid payments, leading to incorrect balance calculations and access decisions.

ย 

Key Rule

Only a Received status (or equivalent) should be treated as a completed payment. Pending and Rejected must be excluded from any logic that calculates whether a student has paid.

ย 

Status Reference

Status

Counts Toward Balance?

What It Means

Pending

No

Payment initiated but not yet processed. Common with ACH/checking account payments.

Rejected

No

Payment failed during processing. Student must retry via a new payment link.

Received

Yes

Payment successfully completed. This is the only status that should be treated as paid.

ย 

Impact on Net Payment Balance

Pending

A Pending payment is in progress โ€” typically an ACH/checking account transfer that has not yet cleared. It should not be counted as payment received.

โ€ขย ย ย ย ย ย  ACH payments typically resolve within 5 business days (excluding weekends and bank holidays)

โ€ขย ย ย ย ย ย  If still pending after 7 business days, submit a support ticket under the Slate Payments category

โ€ขย ย ย ย ย ย  Any rule or query evaluating payment status should exclude Pending from balance calculations

Rejected

A Rejected payment failed during processing and is completely invalid. It has no value and does not reduce a student's outstanding balance.

โ€ขย ย ย ย ย ย  Any rule or query evaluating payment status should exclude Rejected from balance calculations

โ€ขย ย ย ย ย ย  Additional rejection detail (for ACH) is available in the Transaction Details > Outcome section

Impact on Portal Access

When a payment is Rejected, the student is not automatically returned to a payment-ready state. They lose access to the payment portal with no path to retry on their own.

ย 

Staff Action Required

The system does not re-initiate payment after a rejection.

A staff member must manually provide the student with a new payment link before they can retry.

ย 

Steps When a Payment Is Rejected

1.ย ย ย ย ย  Confirm the rejection in Payment Activity

2.ย ย ย ย  Check Transaction Details > Outcome for the rejection reason (Slate Payments / ACH only)

3.ย ย ย ย  Verify the student still has an outstanding balance

4.ย ย ย ย  Manually send the student a new payment link

Updating Rules and Automations

Any rule, query, or automation that evaluates whether a student has paid should be audited to ensure the following:

โ€ขย ย ย ย ย ย  Pending and Rejected statuses are excluded from payment calculations

โ€ขย ย ย ย ย ย  Only Received (or equivalent) is treated as a completed payment

โ€ขย ย ย ย ย ย  Checklist updates, access changes, and other downstream actions should only trigger on confirmed paymentย 

Knowledge Base References

The official Slate documentation does not currently address how Pending or Rejected statuses affect net balance calculations or automation logic. These articles provide useful general context: