Module Area: Billing & Invoicing Procedures
Audience: Visp.net End-Users / Administrators
Applies To: Subscriber Profile → Billing Options → Grace Period & Amount
Purpose
This guide explains the Grace Period and Grace Amount features in Visp.net billing — what each one does, how they work together as a dual-threshold safety net, how to configure them on a subscriber profile, and how they interact with Late Fee settings and automated enforcement actions. Correct configuration of these fields prevents premature penalties on customers with minor or recently-due balances while maintaining a clear path to enforcement for genuinely delinquent accounts.
Prerequisites
| Requirement | Details |
|---|---|
| Visp.net Login | Logged in with Admin-level permissions to modify billing options |
| Subscriber Access | The target subscriber’s profile is open and the Billing Options section is visible |
| Billing Days Configured | The subscriber’s Invoice Due Day and Past Due After values are already set — these define when the grace window begins |
| Late Fee Settings Reviewed | You understand whether a Late Fee is enabled for this subscriber, as it interacts directly with grace configurations |
Section 1: Definitions — What Each Field Means
1.1 Grace Period
The Grace Period is a specified number of days after the invoice’s Due Date during which the account is still considered to be in good standing, even if payment has not yet been received. It provides a short, forgiving window before any billing consequences — such as late fees or service suspension — are evaluated.
Example: If the Invoice Due Day is the 5th and the Grace Period is 10 days, the account remains in good standing until the 15th (5th + 10 days), regardless of whether payment has been made.
What the Grace Period does NOT do:
- It does not change the Invoice Due Day itself. The due date remains the official payment deadline.
- It does not guarantee that consequences are applied on day 11. The Grace Amount threshold is also evaluated (see Section 2).
1.2 Grace Amount
The Grace Amount is a monetary threshold for good standing — not a fee. As long as the subscriber’s outstanding balance is less than or equal to the configured Grace Amount, the account remains in good standing, even if the original due date has passed.
Example: If the Grace Amount is $5.00 and a subscriber has an outstanding balance of $4.50, the account is still in good standing. If the outstanding balance is $10.00, the balance exceeds the Grace Amount threshold, and billing consequences may be evaluated.
Critical distinction: The Grace Amount is not a fee charged to the subscriber. It is a tolerance threshold. An older documentation reference may describe it as a "fee amount applied after grace period" — this is incorrect and has been superseded by the definition above.
| If the outstanding balance is… | And the Grace Amount is… | Then the account is… |
|---|---|---|
| $4.50 | $5.00 | In good standing (balance ≤ threshold) |
| $5.00 | $5.00 | In good standing (balance ≤ threshold) |
| $10.00 | $5.00 | Eligible for consequences (balance > threshold) |
| $0.00 | $5.00 | In good standing (no balance due) |
Section 2: How Grace Period and Grace Amount Work Together
These two fields form a dual-threshold model. Both conditions must be cleared before billing consequences are triggered.
The Decision Logic:
Is the Grace Period expired?
│
Yes ─┴─ No ──→ Account remains in good standing. No consequences.
│
▼
Is the outstanding balance GREATER THAN the Grace Amount?
│
Yes ─┴─ No ──→ Account remains in good standing. Balance is within tolerance.
│
▼
Billing consequences may be triggered:
• Late Fee assessment
• Auto-Suspend (if configured)
• Other enforcement actions
Walkthrough Scenario:
A subscriber has the following configuration:
- Invoice Due Day: 5th
- Grace Period: 10 days
- Grace Amount: $5.00
- Late Fee: Enabled, $10.00 flat, applied 1 day after past due
| Date | Outstanding Balance | Grace Period Expired? | Balance > $5.00? | Result |
|---|---|---|---|---|
| March 6th | $50.00 | No (day 1 of 10) | — | Account in good standing. No action. |
| March 14th | $50.00 | No (day 9 of 10) | — | Account in good standing. No action. |
| March 16th | $50.00 | Yes (day 11) | Yes ($50 > $5) | Both thresholds cleared. Late fee may apply. Auto-suspend may trigger. |
| March 16th | $3.00 | Yes (day 11) | No ($3 ≤ $5) | Grace Amount shields the account. No consequences. |
The dual-threshold model ensures that a customer is only penalized when both (a) enough time has passed AND (b) the amount at stake is material.
Section 3: Step-by-Step — Configuring Grace Period & Amount in Visp.net
- From the left sidebar navigation, select Subscribers.
- Locate the subscriber using the list view or search bar, then click the subscriber’s Name or Subscriber ID to open their profile.
- Scroll to the Billing Options section within the subscriber profile.
- Locate the Grace Period & Amount checkbox. Check the box to enable the feature.
- Click the associated link — displayed as, for example, "10 days, 5.00" — to open the configuration pop-up.
- In the configuration dialog, set the following:
- Days: The number of days after the Invoice Due Day that constitute the grace period (e.g.,
10). - Amount: The monetary threshold below which the account remains in good standing (e.g.,
5.00). - Fee Type: Choose between Default (inherits the globally configured setting) or Custom (a subscriber-specific override).
- Days: The number of days after the Invoice Due Day that constitute the grace period (e.g.,
- Click Save within the configuration pop-up to confirm the grace settings.
- Click Save at the top or bottom of the Billing Options section to commit all changes to the subscriber profile.
💡 Pro-Tip: After saving, verify your configuration by noting the updated link text in the Billing Options section. It should now reflect your chosen values (e.g., "10 days, 5.00").
Section 4: Relationship Between Grace Period & Amount and Late Fee Settings
The Grace Period & Amount and the Late Fee configuration operate in sequence — the grace settings always precede late fee assessment.
Sequence of Evaluation:
Invoice Due Day
↓
Grace Period (days after due date)
↓
Grace Amount (balance threshold check)
↓ (only if grace period expired AND balance > grace amount)
Late Fee assessment
↓
Auto-Suspend / Auto-Delete (if configured)
Key Rules:
| Rule | Explanation |
|---|---|
| Grace precedes Late Fee | A Late Fee is only assessed after the grace period has fully expired and the outstanding balance exceeds the Grace Amount. |
| Late Fee timing is independent | The Late Fee configuration has its own timing field — typically "Days after Past Due." This clock starts after the grace window closes. |
| Grace Amount shields small balances | Even if the grace period has expired, a balance at or below the Grace Amount prevents the Late Fee from triggering. |
| Both can be subscriber-specific | Like all Billing Options, Grace Period & Amount and Late Fee settings can be customized per subscriber, overriding global defaults. |
Configuration Example:
| Field | Value | Effect |
|---|---|---|
| Invoice Due Day | 5th | Payment due on the 5th |
| Grace Period | 10 days | Good standing through the 15th |
| Grace Amount | $5.00 | Balances ≤ $5.00 remain shielded |
| Past Due After | 3 days | Invoice becomes past due on the 8th (before grace expires — but grace still applies) |
| Late Fee | $10.00, applied 1 day after past due | Late fee assessed on the 16th, only if balance > $5.00 |
⚠️ Warning: If the Past Due After value is shorter than the Grace Period, the invoice may technically be flagged as past due during the grace window. The Grace Period & Amount still shields the subscriber from penalties, but ensure your Set Auto Actions are configured with the correct trigger condition to avoid premature enforcement during the grace window.
Section 5: Business Rationale — Why Use Both?
ISPs configure both a Grace Period and a Grace Amount to implement a tiered, fair approach to delinquency management:
| Objective | How It’s Achieved |
|---|---|
| Customer Flexibility | The Grace Period gives customers extra time to pay without penalty, improving satisfaction and reducing support calls. |
| Reduced Administrative Overhead | The Grace Amount prevents the system from triggering late fees, suspension, or staff alerts for trivially small balances — eliminating noise from minor discrepancies. |
| Fairness | Customers are not penalized for balances that are immaterial or easily overlooked. Only meaningful delinquencies escalate. |
| Nuanced Enforcement | The dual-threshold model allows the ISP to escalate consequences progressively: time buffer first, amount materiality second, enforcement third. |
Conclusion
The Grace Period and Grace Amount together form a dual-threshold safety net that prevents unnecessary billing penalties. The Grace Period provides a time buffer after the due date, while the Grace Amount provides a monetary tolerance below which consequences are suppressed. Both thresholds must be cleared — the period must expire and the balance must exceed the amount — before late fees or auto-actions are triggered. Configure these fields thoughtfully in the Billing Options section of each subscriber profile to balance customer goodwill with operational enforcement.
Pro-Tips & Warnings (Consolidated)
- The Grace Amount is a threshold, not a fee. It is never charged to the subscriber. It only determines whether the account is shielded from consequences.
- Both conditions must be met for consequences to trigger: grace period expired AND balance above the grace amount.
- Grace settings override global defaults when configured at the subscriber level.
- Past Due After and Grace Period can overlap. Configure them with awareness of each other’s timelines to avoid confusing states.
- Always review Auto Actions after setting grace values. An Auto-Suspend set to fire "if Past Due" may trigger unexpectedly if the grace period and past-due timing are misaligned.
- Communicate grace terms to customers. A customer who understands their grace window is more likely to pay within it, reducing collections overhead.
- Verify by testing: After configuring, simulate a small overdue balance to confirm the system treats it as shielded before rolling out broadly.