Charge-date rules: how they affect Additions in ConnectWise

Appxite Updated by Appxite

Introduction

Every invoice line synced from the Platform to ConnectWise creates or updates an Addition on the mapped Agreement. Two fields on that Addition are controlled by the charge-date rules you configure on the Platform's Settings → ConnectWise → Configuration tab:

Platform field (Invoices tab) ConnectWise Addition field
Charge Start Date → Effective Date
Charge End Date → Cancelled Date

The exact value ConnectWise receives depends on three things: the Charge Type of the line, whether a configuration rule has been applied, and whether the user has applied a manual override. Understanding the distinction between Charge Types is essential because recurring and one-time lines follow different default logic:

Category Charge Types Addition behaviour in ConnectWise
Recurring CycleFee, PurchaseFee One persistent Addition per Subscription — updated on each sync if values change
One-time Correction, UsageFee, ItemFee, OneTimeFee, UserCorrection Addition created or updated on each sync

The badge on the date columns on the Platform's Invoices tab is the definitive indicator of which value ConnectWise will receive:

Badge Meaning What ConnectWise receives
no badge No rule configured, no manual override Default behaviour — differs by Charge Type (see scenarios below)
System Updated A configuration rule was applied during load The rule-calculated date
User Updated A user manually entered a date on the Invoices tab The manually entered date — always takes precedence over any rule

Catalog.

NOTE! Configuration rules are applied at the moment invoice lines are loaded (when you click Load Invoices), not at the moment of sync. You can adjust rules after loading — changes apply to lines loaded after that point. Already-loaded lines keep the date that was calculated at load time. Already-synced Additions in ConnectWise are never retroactively updated when you change a rule.
 

1. Charge End Date rules → Cancelled Date on Addition

Where to configure: 

Settings → ConnectWise → Configuration → Charge End Date Configuration.

Rules are set per Charge Type. Available rules: Last day of invoice month and First day of following month. A Charge Type can have only one rule at a time. If no rule is configured for a given Charge Type, the default behaviour applies — and that default differs between recurring and one-time lines.
 

Scenario A No rule configured — recurring line (CycleFee, PurchaseFee)

No Charge End Date rule is set for the Charge Type of this line. The line is recurring — Charge Type is CycleFee or PurchaseFee.

When no rule applies and no manual override has been set, the Cancelled Date is not sent to ConnectWise at all. The Addition is left open-ended and continues to be billed every cycle indefinitely until a Cancelled Date is set manually in ConnectWise.

Configuration tab

The Charge End Date Configuration section has no rules added — the rule list is empty.

Platform — Invoices tab

The Charge End Date column shows a date value. The date shown on the Platform (e.g. same date as Charge Start Date, or one month later) is stored internally but is not sent to ConnectWise for recurring lines when no rule is configured. no badge is shown.

ConnectWise — Addition detail

Cancelled Date = empty. The Addition continues billing every cycle. ConnectWise includes this Addition on every future invoice for the Agreement until the Cancelled Date is manually set.

Scenario B No rule configured — one-time line (Correction, UsageFee, ItemFee, OneTimeFee, UserCorrection)

No Charge End Date rule is set for the Charge Type of this line. The line is one-time — Charge Type is Correction, UsageFee, ItemFee, OneTimeFee, or UserCorrection.

The default Cancelled Date for one-time lines is the last day of the charge start month. However, a safety check applies: if the calculated last day of the month falls on or before the Effective Date, the Cancelled Date is shifted to Effective Date + 1 day instead. This is why some one-time lines may show a Cancelled Date in the following month rather than the last day of the start month.

NOTE! The safety check (Effective Date + 1 day) is triggered when the Effective Date is calculated from the Subscription Start Date and falls later than the last day of the charge start month. This can happen when a subscription started mid-month and the Effective Date is clamped or adjusted. See the Charge Start Date — Scenario B for more detail on Effective Date calculation.

Configuration tab

The Charge End Date Configuration section has no rules added — same as Scenario A.

Platform — Invoices tab

The Charge End Date column shows the last day of the charge start month. no badge is shown.

Example: Charge Start Date 01 May 2026 → Charge End Date = 31 May 2026. No badge.

Example with safety check triggered: if Effective Date in CW is calculated as 19 May 2026 and last day of May is 31 May 2026, Cancelled Date = 31 May 2026 (normal). But if Effective Date were calculated as 01 June 2026 (past end of May), Cancelled Date = 02 June 2026 (Effective Date + 1 day).

ConnectWise — Addition detail

Cancelled Date = 31/05/2026 — the last day of the charge start month. If the safety check was triggered, Cancelled Date = Effective Date + 1 day instead.

Scenario C Rule configured — "Last day of invoice month" (applies to any Charge Type)

A Charge End Date rule set to Last day of invoice month is configured for one or more Charge Types. This rule overrides the default behaviour for both recurring and one-time lines — the Cancelled Date is set to the last day of the invoice month regardless of the Charge Type.

Configuration tab

The Charge End Date Configuration section has a rule row with the target Charge Type and the rule set to Last day of previous month.

Platform — Invoices tab

The Charge End Date column shows the last day of the invoice month with a System Updated badge.

Example: invoice month is June 2026, Charge Start Date 01 June 2026 → Charge End Date = 30 June 2026 System Updated.

ConnectWise — Addition detail

Cancelled Date = 31/06/2026 — the last day of the invoice month. For a recurring line this means the Addition will stop billing after June — without this rule the Cancelled Date would have been empty (Scenario A).

Scenario D Rule configured — "First day of following month" (applies to any Charge Type)

A Charge End Date rule set to First day of following month is configured for one or more Charge Types. The Cancelled Date is set to the first day of the month after the invoice month.

Configuration tab

The Charge End Date Configuration section has a rule row with the target Charge Type and the rule set to First day of next month.

Platform — Invoices tab

The Charge End Date column shows the first day of the following month with a System Updated badge.

Example: invoice month is June 2026, Charge Start Date 01 June 2026 → Charge End Date = 01 July 2026 System Updated.

ConnectWise — Addition detail

Cancelled Date = 01/07/2026 — the first day of the month following the invoice month.

Scenario E Manual override — user-entered Charge End Date

A user has manually edited the Charge End Date on the Invoices tab for a specific line. A manual override always takes precedence over any configured rule and applies to all Charge Types — both recurring and one-time.

Platform — Invoices tab (before sync)

The Charge End Date column shows the manually entered date with a User Updated badge. If a rule was previously applied, the System Updated badge is replaced by User Updated.

Example: line where the rule would produce 01 July 2026, but the user has entered 30 June 2026 manually → Charge End Date = 30 June 2026 User Updated.

ConnectWise — Addition detail

Cancelled Date = 30/06/2026 — the exact date the user entered. The configured rule (if any) is bypassed.

2. Charge Start Date rules → Effective Date on Addition

Where to configure: 

Settings → ConnectWise → Configuration → Charge Start Date Configuration

Rules are set per Billing Cycle. The only available rule is First day of next month — charge start dates for lines in the matching Billing Cycle are adjusted forward to the first day of the month following the invoice date. 

 

If no rule is configured, the default behaviour applies — and that default differs between one-time and recurring lines because recurring lines use the Subscription Start Date, not the Charge Start Date shown on the Platform.

 

Warning! Recurring lines and the Agreement BillStartDate: For all Charge Types, if the calculated Effective Date falls before the Agreement's Billing Start Date in ConnectWise, the Agreement's Billing Start Date is used instead. This is a ConnectWise constraint, not a Platform rule. If you see an unexpected Effective Date in CW that is later than what the Platform shows, check the Agreement's Billing Start Date field in ConnectWise.

 

Scenario A No rule configured — one-time line (Correction, UsageFee, ItemFee, OneTimeFee, UserCorrection)

No Charge Start Date rule is configured. The line is one-time. The Effective Date sent to ConnectWise is the Charge Start Date exactly as stored — no adjustment is applied.

Configuration tab

The Charge Start Date Configuration section has no rules added.

Platform — Invoices tab

The Charge Start Date column shows the raw Platform date. No badge is shown.

Example: Charge Start Date = 14 May 2026. No badge.

ConnectWise — Addition detail

Effective Date = 14/05/2026 — the Charge Start Date exactly as it appears on the Platform, with no adjustment.

Scenario B No rule configured — recurring line (CycleFee, PurchaseFee)

No Charge Start Date rule is configured. The line is recurring — Charge Type is CycleFee or PurchaseFee.

For recurring lines with no rule, the Effective Date sent to ConnectWise is not the Charge Start Date shown on the Platform Invoices tab. Instead, it is the Subscription Start Date — the date the subscription originally started. This date is clamped to a minimum of Invoice Date minus one month to prevent sending dates too far in the past. The Charge Start Date shown on the Platform is not used.

NOTE! This is why the Effective Date on recurring Additions in ConnectWise may not match the Charge Start Date you see on the Platform's Invoices tab. For recurring lines with no rule, the Platform uses the Subscription Start Date, which may be earlier — clamped to Invoice Date minus one month. If the Agreement's Billing Start Date is later than the calculated date, the Billing Start Date is used instead.

Platform — Invoices tab

The Charge Start Date column shows the charge start date for the invoice period. no badge is shown. This date is not what ConnectWise receives for recurring lines — the Subscription Start Date is used instead.

ConnectWise — Addition detail

Effective Date = Subscription Start Date (clamped to minimum Invoice Date − 1 month). This may be earlier than the Charge Start Date shown on the Platform, and may differ from month to month if the subscription was recently created.

Scenario C Rule configured — "First day of next month" (applies to any Charge Type)

A Charge Start Date rule set to First day of next month is configured for the relevant Billing Cycle. Charge Start Dates for lines with that Billing Cycle are adjusted forward to the first day of the month following the invoice date.

Configuration tab

The Charge Start Date Configuration section has a rule row with the relevant Billing Cycle and the rule set to First day of next month.

Platform — Invoices tab

The Charge Start Date column shows the adjusted date with a System Updated badge.

Example: invoice date is in January 2026, original Charge Start Date 15 May 2026 → Charge Start Date shows 01 June 2026 System Updated.

ConnectWise — Addition detail

Effective Date = 01/06/2026 — the first day of the month following the invoice date. ConnectWise receives the adjusted date, not the original Platform date.

Scenario D Manual override — user-entered Charge Start Date

A user has manually edited the Charge Start Date on the Invoices tab for a specific line. A manual override always takes precedence over any configured rule and applies to all Charge Types — both recurring and one-time. For recurring lines, the manually entered date is used instead of the Subscription Start Date.

Platform — Invoices tab (before sync)

The Charge Start Date column shows the manually entered date with a User Updated badge.

Example: rule would produce 01 June2026, but the user has entered 08 June 2026 → Charge Start Date = 08 June 2026 User Updated.

ConnectWise — Addition detail

Effective Date = 19/05/2026 — the exact date the user entered. Any configured rule and the Subscription Start Date logic are both bypassed. The Agreement BillStartDate clamp still applies — if 19/05/2026 is before the Agreement's Billing Start Date, the Billing Start Date is used instead.

3. Quick reference summary

Charge End Date → Cancelled Date

Scenario Charge Type Rule configured? Platform badge CW Cancelled Date
A Recurring (CycleFee PurchaseFee) No no badge Empty — Addition bills indefinitely
B One-time (Correction UsageFee ItemFee OneTimeFee UserCorrection) No no badge Last day of charge start month (or Effective Date + 1 day if safety check triggers)
C Any Yes — Last day of invoice month System Updated Last day of invoice month
D Any Yes — First day of following month System Updated First day of following month
E Any Any User Updated Exact date entered by user

Charge Start Date → Effective Date

Scenario Charge Type Rule configured? Platform badge CW Effective Date
A One-time No no badge Charge Start Date as stored — no adjustment
B Recurring (CycleFee PurchaseFee) No no badge Subscription Start Date (clamped to Invoice Date − 1 month minimum, then clamped to Agreement BillStartDate)
C Any Yes — First day of next month System Updated First day of month following invoice date
D Any Any User Updated Exact date entered by user (still clamped to Agreement BillStartDate)
Precedence rule: User Updated always overrides System Updated. If a user manually edits a date that had a System Updated badge, the User Updated badge replaces it and the manually entered value is what ConnectWise receives. The Agreement BillStartDate clamp is the only constraint that can override a User Updated date.

Summary

The charge-date rules on the Platform's Configuration tab give Partners control over the exact dates that ConnectWise stores on Additions. The key points to remember:

  • Recurring lines (CycleFee, PurchaseFee) and one-time lines (Correction, UsageFee, ItemFee, OneTimeFee, UserCorrection) behave differently when no rule is configured — recurring lines default to an open-ended Addition (no Cancelled Date), while one-time lines default to the last day of the charge start month.
  • For recurring lines with no Charge Start Date rule, ConnectWise receives the Subscription Start Date, not the Charge Start Date shown on the Platform Invoices tab.
  • The badge on the date columns is the authoritative indicator: no badge = default behaviour, System Updated = rule applied, User Updated = manual override taking precedence over everything.
  • Rules are applied at load time, not at sync time. Changing a rule after loading invoices only affects lines loaded after that point.
  • The Agreement's Billing Start Date in ConnectWise is a hard floor — no Effective Date sent by the Platform can be earlier than it.

Related articles

compliant ConnectWise

Was this article helpful?

0 out of 0 found this helpful

Articles in this section

Add comment

Please sign in to leave a comment.