Save manual as PDF or print  


NCRC Recurring Contracts


Contracts for automated invoice creation and billing.

Current Version: 21.1.3.1 as of Business Central 21.
AppSource Name: NCRC Recurring Contracts

Manual


Creation date: 2024/11/22
The current version of this manual can be found at:

https://www.navax.app/help.php?AppID=NCRC&L=en


☰ Contents



General

  • NCRC Recurring Contracts
    NCRC Recurring Contracts adds contracts to Microsoft Dynamics 365 Business Central for automated invoice creation and billing...

Working With The App

  • Contract Creation

    • Customer Contract
    • Vendor Contract
  • Billing

    • Customer Contract
      Click the Create Sales Invoice button at the Contract header or in the Contract overview...
    • Vendor Contract
      Unlike sales invoices from Contracts, purchase invoices are not collected from the Contract...
  • Dimensions

    • Dimension Setup
    • Dimensions in Contract
      For line-level actions that cause the Payment Plan to be regenerated, dimension value changes can be entered directly in the associated input mask...
  • Payment Plan

    • Working With Payment Plan
      The Payment Plan defines when and how much will be invoiced...
    • Payment Plan and Start of Period
      The default Day of Period Start is defined in the NCRC Recurring Contracts setup and is transferred from there to the Contract header and thus also to the Contract lines...
  • One-Time Payment

    • Working With One-Time Payments
      To process one-off contract components, lines can be marked as one-time payments which result in the line being marked as completed as soon as the sales invoice has been posted...
  • Indexing

    • Indexing Setup
      In the Contract setup in the Indexing tab, an index status must be entered, as well as the rounding precision...
    • Working With Indexing
    • Working With Retrospective Indexing
  • Cancellation

    • Working With Cancellation
      Cancellation of a Contract or a Contract line takes place at the customer's request and must happen within deadlines defined at the Contract header...
  • Extension

    • Working With Manual Extension
      Contracts can be extended by a defined interval...
    • Working With Auto. Extension
  • End Contract

    • Working With Auto. Ending
      Once a Contract line has been fully invoiced and is no longer to be extended, the status can be set to Ended via a Job queue entry, thus marking the Contract line as closed...
  • Job Integration

    • Job Setup
      Activate Job integration to create Jobs for Contracts...
    • Working With Job
      Use the Create Project action to create a project for a Contract. The project number is then entered in the corresponding field at the Contract header as well as the Contract lines...
    • Working With Job And Contract
      You can connect a Customer Contract and a Vendor Contract using a Job, thereby comparing the actual values from the purchase invoices and sales invoices. To do this, first create the Customer Contract and create a Job...
  • Prepayment

    • Prepayment Setup
      To manage Prepayment, you must enable Job Integration in the NCRC Recurring Contracts Setup...
    • Working With Prepayment
  • Consumption Based

    • Consumption Based Setup
      To be able to invoice at cost, you must activate Job Integration in the NCRC Recurring Contracts Setup...
    • Working With Consumption Based
  • Scheduled Change

    • Scheduled Change Setup
      To use Scheduled Changes, you must enable them in the NCRC Recurring Contracts Setup...
    • Working With Qty. Increase
      An increase in quantity, for a period already invoiced, results in a sales invoice for one or more periods...
    • Working With Price Increase
      An increase in the price, for a period already invoiced, results in a sales invoice for one or more periods...
    • Working With Qty. Decrease
      A decrease in quantity, for a period already invoiced, results in a sales credit to one or more periods...
    • Working With Price Decrease
      A decrease in the price, for a period already invoiced, results in a sales credit memo to one or more periods...
    • Working With Qty. Change in Future Periods
      A change does not result in the creation of documents it only adjusts the payment schedule...
    • Working With Price Change in Future Periods
      A change does not result in the creation of documents it only adjusts the payment schedule...
    • Working With Date Change
      There is the possibility to change the start and end date of a Contract line afterwards. To do this, open Functions > Scheduled Date Changes on the Contract line. You can then enter a new start or end date...
  • Bundles

    • Working With Bundles

Setup

  • NCRC Recurring Contracts Setup
    Here you can specify the general settings and defaults for the NCRC Recurring Contracts...

Appendix

  • NAVAX License Management
    The NAVAX License Management page (in older versions NAVAX License Overview or NCEX License Overview) displays the current license status of the NAVAX extensions...
  • Installation Notes
  • Release Notes

Docs  /  NCRC Recurring Contracts  /  General
 NCRC Recurring Contracts

NCRC Recurring Contracts adds contracts to Microsoft Dynamics 365 Business Central for automated invoice creation and billing.

Navigation

The NCRC Recurring Contracts is integrated into its own Contract Processor roles. Fields, actions, pages and reports originating from the NCRC Recurring Contracts extension are identified by the abbreviation NCRC. This additional labeling makes them clearly distinguishable from other extensions (which may use similar names and designations). The search terms "nvxrc", "ncrc" and "navax" are also recognized by "Tell me what you want to do". This allows very fast access to the individual areas of NCRC Recurring Contracts.

Note

The NCRC Recurring Contracts was developed with the prefix NCRC resp. NVXRC. NCRC resp. NVXRC stands for NAVAX Consulting resp. NAVAX Recurring Contracts.

Permission Sets

The following permission sets are available for NCRC Recurring Contracts:
NameDescription
NVXRCNCRC Recurring Contracts You need these permissions to use NCRC Recurring Contracts.
NVXRC SetupNCRC Setup Recurring Contracts You need these permissions to set up NCRC Recurring Contracts. For more information, see Setup, NCRC Recurring Contracts Setup.

Installation Notes

For more information, see Appendix, Installation Notes.

Docs  /  NCRC Recurring Contracts  /  Working With The App  /  Contract Creation
 Customer Contract

Creating A New Contract

Open the page Contract List and click on New. The following values should be entered at the Contract header:
FieldDescription
Starting DateDefines the start date of the entire Contract
The value entered here is transferred to the Contract lines, but can be changed per Contract line.
Ending DateDefines the end date of the entire Contract
The value entered here is transferred to the Contract lines, but can be changed per Contract line.
Billing TypeDefines how often to invoice (monthly, quarterly, annually, etc.)
Source TypeCustomer
No.Customer No.
For more information, see Contract Card. In addition, define default values for the Contract lines for the Cancellation and Indexing sections. As soon as the Contract number, the origin number and the Customer number have been entered in the Contract header, you can enter the Contract line. The status in the Contract line cannot be edited. When a new Contract is created, the default status from the NCRC Recurring Contracts Setup is automatically applied. Status changes can only be made using the associated feature. Select the type and No. of the object (Item, G/L Account, Resource) you want to invoice your Customer and enter the quantity as well as the price per invoicing period. All other values are taken from the Contract header and can be adjusted per Contract line.

Create new Contract from Sales Quote/Sales Order

In the sales quote/sales order, under Actions > Function > NCRC Recurring Contracts > Create New Contract, select to create a new Contract. A new page then opens where you can enter Contract-specific information. The values are then transferred to the Contract header and automatically applied to the Contract lines. The sales offer or sales order can then be deleted (or archived). In the newly created Contract, the values from the offer or order lines are automatically transferred to the Contract lines, whereby the quantity in the offer/order then corresponds to the quantity to be invoiced per period. Change the status, to the Active status defined in the NCRC Recurring Contracts Setup, to generate invoices from your Contract.

Adding Sales Offer/Sales Order Lines to existing Contract

If a Contract already exists for a customer, you can also add offer or order lines to it. To do this, use Actions > Function > NCRC Recurring Contracts > Add lines to existing Contract. A selection list of all Contracts will then open for the Customer and the desired Contract can be selected. The sales line is then created as a new line in the Contract. Further Stepts see Billing

Docs  /  NCRC Recurring Contracts  /  Working With The App  /  Contract Creation
 Vendor Contract

Create new Contract

Vendor Contracts must be compulsorily created from purchase requests or purchase orders. For the creation as well as the correct posting of purchase invoices to Vendor Contracts from purchase inquiries or purchase orders, it is mandatory to activate the archiving of inquiries/purchase orders.

Important

Activate archiving under Purchases & Payables Setup > Archive Quotes > Always & Archive Orders.
Enter a purchase request or purchase order. To convert it into a Contract, choose Actions > Function > NCRC Recurring Contracts > Create New Contract. A new page then opens where you can enter Contract-specific information. The values are then transferred to the Contract header and automatically applied to the Contract lines. The purchase request or purchase order can then be deleted (or archived). In the newly created Contract, the values from the inquiry or order line are automatically transferred to the Contract line, whereby the quantity in the offer/order then corresponds to the quantity to be invoiced per period. Change the status to the Active status defined in the NCRC Recurring Contracts Setup to assign purchase invoices to the Contract.

Adding Request/Order Lines To Existing Contract

If a Contract already exists for a Vendor, you can also add request or order lines to it. To do this, use Actions > Function > NCRC Recurring Contracts > Add lines to existing Contract. A selection list of all Contracts will then open for the Vendor and the desired Contract can be selected. The purchase line is then created as a new line in the Contract. Further Stepts see Billing

Docs  /  NCRC Recurring Contracts  /  Working With The App  /  Billing
 Customer Contract

Click the Create Sales Invoice button at the Contract header or in the Contract overview.

Options

Bill Until DateSpecify the date up to which the invoices should be created
Document DateSpecify the document date of the sales invoice to be created
Posting DateSpecify the posting date of the sales invoice to be created. By specifically setting the posting date, you can control an allocation in advance or in retrospect.
Do Not Create Invoice for PeriodIf enabled, all periods up to the Settlement to date will be marked as Invoiced in the payment schedule without creating an actual document.
Combine PeriodsDefines whether you want to create one invoice per period to be charged, or one invoice for all periods.
Create Invoices perDefines at which level the invoice will be created:
  • Contract Line
  • Contract

Customer (Requires the "Combine invoices" indicator to be set in the required contracts).
The created, unposted sales invoice is visible in the Payment Plan and can be accessed from here. If you want to delete the unposted invoice, you can either run the Correct Billing feature in the Payment Plan or open the invoice and delete it there. The period is then marked again in the Payment Plan as not invoiced and can be offset. To post the invoice, open the document and click Post. In the Payment Plan the posted invoice No. will be entered. If you need to cancel the posted invoice, use either the associated function in the Payment Plan or the standard functions (Cancel Sales Invoice, Correct Sales Invoice) in the sales invoice. This will then post a sales credit memo and allow you to recreate the sales invoice. The original sales invoice as well as the created sales credit memo are attached in the payment schedule as Assigned documents of the period. For each sales invoice line, which is created from a Contract, a remark line is created which gives conclusions about the Contract number and Contract line number, as well as the period. In the NCRC Recurring Contracts Setup you can define if only the period, excl. the Contract number/Contract line number should be printed.

Docs  /  NCRC Recurring Contracts  /  Working With The App  /  Billing
 Vendor Contract

Unlike sales invoices from Contracts, purchase invoices are not collected from the Contract.

Docs  /  NCRC Recurring Contracts  /  Working With The App  /  Dimensions
 Dimension Setup

PNG  IHDR@JsRGBgAMA a pHYsodmIDATx^{TT珧Tk6g[y\+콳||,q #BYK0<`Dr h&3K(4 `0kϧ;~=z螣=UYݣ}NG7ݳ @ h 0-@ hD7sϙ3gƍݟhr#墋.z8SO7nذa_җ4^_u[c4^jMiAɓ?߯,4/}Kk֬/^"YWW,wyM{s=~K06m8Yvڇ~ l͚5_yS d/^wuuCdݵ_~dvr^{ӧOk^zIiF-*̥%=Z#5,!mp&O\;i z}v]'?e1w=;IS,_FctWlVjfGuC_vr^Ք6 =^2miXu#h6鉎Bm;:8(NsH'[yÎ)3cOm/ϛ2[2|ڒp:E]?Sski vPYs H׳=a0,wI 7Ԣu[B[j0 wnhQZf+ӧO۫ʚ<հ<عxW) to[o}G=FUU `УFMnXĩy]Uw%to{ÌT}wyD/(O5<}ko`W;=lήm+luӢGΎRy:|/o~?hiZ)w,s2zRij]bMe]GOZvO1OlYg;tħ_pݴe o2ꎌc P.ڻwO?oouI*Sym2bFy695oku79׌3li!5Wݵێm[QCw2~/jr{hǶ;u3gKhG=Rܤ%{vuߌtuoH+tk_O=ZwJ5z|{ٲ%˖Xu0ʦg |G\.]M& ,Qx+͛9oن-|rGGa üBMoEfײU+v=pKcK-;Ozv[Ƀw!@ ^~''Nկ~ecǏ9sK/dc0.OPu`Yi(]x+_׉{˜3{Fwvm`:n:m Ikoϙ3gܸq~Dp?crna\OeRE[u|kQ)ww+tDWX~+l]63%=+??l}+\rpfBzDYa2$ȇy}+_9{ow?!?醮).bv="3.;=RxGע5aqɃy/u~Isd_g;xreذy[vϯ뺍7V5{]UOBQ>i~T wGÇ`D\J۳zI3uv?1q4t-9m^t$Ӽ}Ghf\v&-ÞgOs{gf,{7iII[4;Į%'9?#<uVZ=-b#1 WGώ?*}4q>8Ek!޳"|(ruJ-PP|T1ePi;VJoG2 pJW.+vߣEYUˏyl{=U5zvH+=J :8V `{quo{:z4aߋY~cXڰi˶kE~JTZEM*)7%_}Ĉ?яGƽ{vtt_T[P4cQǖ]]=tyn8Cuյcѹ,]Y}_=p\>02?|IN o<>}-op mzVe_9%D3ܽm›fUxU<xzU_Gȫ^p 췚S/cz{^><_G'/R=#ٟLtg<uJfEѷ=&JTS-s}* F w}m۶_4g@=G>?Pݥcwڲ}A R.Th_ dh{kUyXwG.jAVvp]5O<-_X,b%F_ӝhI D^eWǼ&M_TXtY/~ޭ${D>o%:Nضc{Oqvm 4}N\Pg{j{4c{ԄwΎ>9o4Hw=[ l ^mɃku脲pWQy?1oђR|kJN׾{8qbƍo.;ۧUw3d?+g{xy]]]GW<Ԙf9}th9 lE߿n, R5mp-qX-NE3rhiFWfڶ"g㯳tgCuvflf< Dzf!Q!ը/a}v{߶eGa%79:c{C;vFGQ.rWwawv-X>Hײ- I3^c+]؋Oğ,NM>iotL &>[V~hҲQ J`<lZ K~c/{6}Y ǂUTۤF ;8^z馛n;~Dƍ6^mtR]N5yZM1+\~Pv,Oe{>Ȕy<2c绖 _?9p)kQ  7.4-w4A]oV% ;}*|O&d~jp pwVOjQӧ5RG5K`dL[rX~*PSQjwϟd-FΘ1Mmhk5:-6Ik3˱il bO#կzӘљZg'[yE{n{yޔLp[? Y<9r4S?c{=15dȐ'N&WⳕQS)T:꫍W1ꮍG5S#5F=diw MlbCDUےep2[vZMy{&dE_m96f)G]tG7Zw4iGookT0 EYHcyF}#7_Mn_ b)V)?7M``b߮8}#Y< `@)-ֳ7 \`Kbk+7[7@#3fuK7Wy|Y~Ey) bi)V唥 `yFZ[϶F[/zF~ٳ84&>h˖-̴5֤I֪/ |8#mt[mfn2n5|tM^sԴ= %rV {MY4-Ml Yc{{#t lkwx߿^9pD*nח@W? o_f~. `QiZ{Z+V/|oN-j- wKyC=v<մZ/ 0 ~_zok5@7B{&xf-ŖhkumJɛ[7Wx_.:|O'^ͮ6߈bj[l7Bg--_,ޘn^{WW>u:ձ}}`~k-B–F4E!O )l}e6yƼwKyF־╫|r;~UAKs~_^XTs4֪Iְ6-EUU_mo{oW_}qϭX'S9l> -ӗk; oj~ `4O lwdjM.-E|%^Wx^pcc}yMj|Aۊ= ?t;i̿Şۿz~!Eom;𣙓t{soxGRgּѓ'o]-7(XWk7_-P~]W鿤ڵ|ͫWd__]o{U>K|89tѯ{?ؖw{yFn cǎw:?g~ˎ߰ݟ|z? }^A?޹~3g<_6l7f듦hO<3Ǟ~W:GT>;֢I?~j~lOOo-Fjơ3>V `#bk*r+_VEX*\CWo_;9X^虏OuE _F_uۧ(㠏81oR.x3_=7jɋzh7l7f?qr'vaO8Qm&5/~aW[{3P7_.Ju /?Տ?nΈj?# ~{o~eqZ/~5kPX@M֯Yѵ;c叏¿?%GOS}Whsغ|G,FGZ];]{`Xݰ1'Ny~}s@kiS_Aj!JxSM}zyjWo)/|X<#=/7?{oW׮]k[k5 FzCK_ ~tAο~T^|Rk~>a4xkЍo\|m* 4J{waׇvZ#3vXBۏ-|~9O횲h!K,M(K=Vٗ_m'oo7ϼ/TЀs7zWr Gཟ|r寞:{>eA+V7H~鱍nظ%9znij.g h|VOB_G8RVQe$' 56jΜ=na7ji-s'p?>X-X֜޾ +V~k ` ~t_-\;xw}珝?cnOn~ `Y1)kw>+t*]={fZ'b8UŚFm6neV~z7';iz|XBsY`ͪ_yẆ`@s1R2Os# 3H/5;J0`A9s执߸,Q~5bz"V_lmLuH}MPl#iV~mO")=#oHml+o߈owڥV"3H\ ozF5d'-;uw/̮G?:vHx+0>=v|ƜCXzu˼mmooU[-4twæ%{dH V,E#}x#|*+Zկ۷~W^Y˪__>K*\ˇ5u/z?>qrw4@|3竁O<Ӌ{_4(\ !bϺC\rFѢmLxR>87KV3/:~c /`ش-gM\v [tVW<{ `կy*Z_:ƒ퇏Xok_G-& _Zbp_u>iic}GӾv?9a ء ]o?t$RúL/](ԯ ]&ޥ 8'}#޾e/+W"8a˟iH4ht@坯]޵,,6-|N}|vO>UW*83O> ~?oگ:6J$Xe#mP׺WjUOS}g>'?u/R݂{u_6X[c[{[/֗_~׬Y5;r&ߋ-7awJukɧ3}lnZ(Ә,WvqSÄ%+-~? =pkyonnx`W|y&_ d{F}+ `yqj߿ZTe|:Tyt_<;Z-X6О5p xV~ר}jAg];z~_iZ-w@^./Q^,oZ,{Ol5 o~r7xVpMxF<SlsRRt_0!}#޾Yo~߿^ ՏjEiZ7Xԡ)!7ǻ+-~<}W<SkL,M坿Z}r}c4Ɋ5SOrm}@[czx9Ldє|3w/rQXk!Z7fibњl`ߞ~8;mlm˿>9OX2u[c4^tsD{5f~hyo,}dikO l&[k`+޾+0;_ ojF @;P8z7B{V}8;m$mo7??@C<󛿞cos? ~XWŋ)dpk`6%o˿h3+viow 宆OF!M{8#J+)[~Ж>dG-}i sGi ƒoygnP U7o7RJla[YW sUi` RT+$+dK}#lR+%) J \x 8jJ,*/f._)`oo~&ֳ9_. `[EoWle+D,zS?#!zy-T_%<7l Bmկx]jg}6)]=\`)_i,}#ULRBKh`P `M9$_a~ `@8^}7 `OVTK";6ߢ7WUZ- +WaŊ6ha `Voz"p*%oJ"8MJjkN|u]}v_&k6l0uԡC|'~3f̺uΜ9e[o mK/TwW^})m%\bsW_}O>y1 ϙ3gȑQG}CzM7[oY? wy뵩>r;x~+2y0wYxFS=+:·~{y)uvZSY'?6l͛.[-E7iӦd_(Ə΅ 6 >\֫k~tuu]uUO@N25=TI /J/^m1b׭[cdf./W:™z衉'tv05_Wgf Rψ@bik6mZ_.H}F 9W T:u;|衇.-*={K/λ 'Ok.#' 4hĈU|td<ٍ7^Zw]{=LJh]7Xm;m?v>QymViu=Ze˓Vs׾hl::pLa?-9sfvvrt4>EGFi^-A/ѩf-׿m[.GNKXfͨQ6{mIᇼϚ5-|pԩ9ߙ]?Z֥5]yvp@QҒ+쑾tHr}=mYNvo~ )cu 9>}Zsε9 6Hѷm̘1~ݽ{W}OJj˓޻#J.l޼yaNh:thꃲuTDj*@hM6M>QJFozC[0:+KPuR~}{w}Ν;5FS}ԍ.%̟?Ȑ!OhJ9s<G~.;rKX2=CmNi;?+FiGhW_}Ϙ5ٳMqӷ&̨o~)YvϿQkLmAw^]`=zԖU_~:i5s=]]]J^{|+L_~& ȅ%\U6hѢcdž=a6lX#І~_E[ `*XjRxK3Y_mY/~[)Eա T,Ij޽yX93Oޫ+< Gj˓z[ ѣSjMY%upj 'N:U bJUM74a$'9ھо޽);::yh҅ #yf@MOO.Vti!~?yTs-_y)hZ{gF)D90dO~Yܼ^9sV]MYO@;("pIW+ ) %bO֩JMrRMG>){Ҧ*RK)SdVbFHkNL2SI_egf,U(U)ZPbʡ#FS)RoT_ӧOIQ"#y Q?wy?nܸdgmkQF-O?T0 ?*܎|0+塃SO]p?2`\e4~6~?Iꫯ޴i@$3%ӲVzM`S%X'NLJjANC;vE4e?pΝ{/[,WWVک|0^S&7lgL2S~}W~~6u̘1!4M$q-OJ5R>Ûʰ$$?[S{w}k_Zr 35^ߧT߿_՗z|9;]ӷL#: 1 uJA_dRt뮻N>mw37z=A"Z^ؓo7!_)d!YFU4[05Y\=q>HWZ'K.ESOLKr6)T2+L2S~KAR2bĈeՎW(j۷+ѣGQ>%G:iHefkw~}Cՙk׮[X{TsԨQ0[arc/jϜ9ꫯ^veԘmI'9sz%$  @HR] RSU `M1mb+ZmmV6lX$dj~=2CVWv?k֬f}hMR[ҕ֛zh+?yĉ5VAf&V?^#U<+0M~ZR`mީno3w}O>(ǎA?!ICG ep5C ob׺ܼ?Q2ZNV,bSLXF,Xf٢}#8K.kN-a6s̹-Sًu:v7'Uz+,O-[h}Pʒ)S6/ry>>7L2SIZZ7?u d0Mi `mz'!E2yWݨ IZoyaZ<{_# ZWS>Mw7/)1y 駟N)HXXEoRl|Q~C-mWhSzGC] .,&]+}W\#֭f$ ]?~$3囤#썤UdC{\-O;ߵ+o0sm^{5SYvo`5*I27/)-Ѻ|&~" `k`f,q{fpgAYcWC~[>EC-L |C]4ג$~?0N*GYi]öڶ_K׾{7nԡKnL7?JzzOʿ*:u sfU}@\YNG~FQk|YH*m@؛S?ZZ~0~)І,,^d/ ˿R=~C[vk:ĩ3~#rJ|ǣF҅xξvvv^qɿ1i3~S*x~%$7I+YIT)9;mJN*&3i Æ -r Rњsz?J~LAe?))!UǧUՙ\>`#_i󴛙o.Jء ӷVb,%ޮ(Bk_@-\~5g [s饗*S8q'?ZW_ p t̤zEݻw_wu7|sfޤJ;~VE`{i[oik/Hg44*& d۾vS;p 9XҊᄏo/ 5rHfG>)5Ν;Hz_%v5פ>|GߝpD'\KH}O}.9O,}Qyoi)HMN sD_jq#P7uM7˿w:)էbj+9f[W~%˿r!]^4JzϿuUV7o~ǯd~g&.͛JZI֮] ?{-ѯ\F6,D?*_|O>ؾ˿"|ܸqU's=]v~lUUa/,Z."ձRMґzF~z( ;C+`k֒5~V\J۪l+42efM9sLTdR<J^gϕkm}k㤻 }[/Bmx6{^WWO+^?ڀm۶>}Zo~<3tH6+µa~E'M?oyutRc-I|4Rᥗ^b iǎ~ӟhP˷Y-2dS? Kd J/j{j/hjT*9D&uu]Wi2] /X@ R= Q0W:FWW^yelL4ֺ~*;3>R-Pv֢u|4͛oYh|rɓ'kSW!MT6a7IGfXN8jmqw)c?[ (Ք&emGD1'|rĈ9єg?+0(޴Lg*, };4A=o<@ zᩧ `93lsZJ+cp5poK2pWԯئh27o" ` l `鱁t_o e˖sw`8ԯ$~/gp oٯKh`XKX_=|˫oΠ_&l /&7pY_@7ش ,HS,қ%g/}#l/+QS Uzym+8Nߒ@7fT`)*/{kd[MxW Z%g`Y `zjX˵ l8䮯pWl|f `ٻŊ5}#lNV /Js0Nz `2b zVbKE?6&) ,NX5lzn)-"Rܵ5E~ `@gA[,^&̀կ8Y\_?ź5P&8 -0?XfDi)jB|89,Mp@*wAڲ/j}j`%mp.~Ŷ#W`@5XHc04h&l[9KRO>df{ƼTRwA{N!~r%9_XK,_COl[=~ @Go?~vel/{v&xF`Y `[Pk<92|pCeÆ M;WPݜ1cF I`\k_v `#U¯|}}g~QMkƋGU'~G8up%XjUl;ћZVaH-v;nhX>w̗ZgIoYgop߂g:z圅 mJkH-Px|Y o]{hh;Sӆ]{j++]kӔpb{rwB*l= 4d[{&x,] IeN5`p4h[JlKR,\sڦd w `@<7j۵‹0xL?3>k$о~%o"bXk X{zFjp<I*mo`_Po.h/H`o»0%w`f3~X4MIKR,X5py+Q-W5p* ¯s/)ڈT- d6{C0&޴M^wA{<+ Y-|fCޫ~`_C$[x4J\ޫ1Xs=G@i60.M)A1~7b+Vm7p~C[;<&N5pfo,kJ^ Ay4@'5g۠b[+)Α>{lGG 45Oۘ.y__u|f3),XpPx޽_W i&m ,40{q95{lWYيn&K*J='NԡH=nK,|rYv5رcݫہ"V_͕Sư;vlܸq1)_xf)`GzС!zuZ%@w/^i'X_u.zZMsĢEicר}-o޴i=kɉ=/00 ]Sp)`{#FZFj̮] txe 4 qfVׄX!#ՄW\qzuرk׮UR:u͛.5'|bSj-7n9r"#Fx5>6erL/[1Zo(HVⱛŧh~G7 LQ[ɖDV7Fnpē5F@%#1Z-d:wd…dmm^moш<%=#042O[iKro7|sȑnڽ{wgg;vR娥?{ZFlݺuر*+bƍ6ˉ']ڵ4}F:ujҥW_}Fj?4ꫯΛ7OfÜ={vݺuBQ̙ 0+[Sp cǎ7Nd-`գwٲew}brĈ7p?Pݽ[㲶o߮[֮]#v%qɅhF5w\ݾk߯Fp_]_~YfiEZi.ozThʫj̙K, Mk͛7k&L\zG?D <+[Sp `kJ/wd~1cBaڣ_~ݻ3:}#G~"?A֌MvEuvvj lrɉ'^qZe?ɍ|4iK. njydVl롕+WCgΜ^k#Y| /leo|ѣlaUW]o>qƌ\r|.!^f]w>:ֱ֭+RZJ=1B=,ZN:ex0<2.z衇ԟ=p2eC\cǎݻwnO.KkOVG}#\|Ŋ{N/,'NXz_i&Nx1|xȑ*tr#lrw}5]tnEC֒3g̞=tM`Yيn&e;cƌ9oMлm-y]vs_>sVz?A^WK'ԩS?~ַ-e㰨h%Oӎ+V\{W^y={l2Ӗ&QU1b!M|ٍ7ڟ%_>sZD̙3mdKO%%'( ;v{% `hm0 Ӗ&y06O[iKp0000000004q@% zHO|8Eyp=Χ >eТhp\xp=p>hp\xp=p>hp\xp=p>hp\xp=p>hp\xp=p>hp\xp=p>hp\xp=p>hp\xp=p>hp\xp=p>hp\xp=p>hp\xp=p>hp\xp=p>hp\xp=p>hp\xp=p>hp\xp=p>hp\xp=p>hp\x  ՌN'0Q8 ׍7oݩ3>5?xtc| `C[mV*JB:Qxԩx#M͜{wog2}s)@ mӶXѧK`[uϏm1sLJmwā|u?6S4%e_wV/ͨٵ- 矿sּ'L:SWn9ͨٵ-`C[mV)R燜85 ,uRڋa9;ǏӹM䭽4 ;- Z kn]}wL]i߁Μj5EiZ?7\x6g+jzշq<4QY9|G4S4%K-sM[@-_^ mӶ XY >dWk@CЗvM᭽XӋ:q-M_u[c£Z8@{ڹ[y6۱n~ 6wX-silK%^ wskl@Nk9i`Χh _T^ 7/[ *aɔsk ~!uyA#µ [\x6Uש~mH56߇/tΧo?`.xhq]4iV<W>/(KxX@~F(3wjӗG *ƛ:;uX1ua>Uu`mp|YFiĪt>-\k&޺pcN-_A+ƌ]k2>,l/E0Vcԕκųkm%NږS~ٿ|jhh-^C5w$5!w J 6%y6I+Rg: ?{  ~VG}i" tms) &ۿ|Ua]'+rfjJc&L> =!uU=dV^t$O& ~T6|dN/u#n=#?w J 6%y6C+R犺FoS0f_iy5ٳ=nJcTwo98 x4=<+GFSO'Ll[W醶E5DbJ&0Kov6kw"x:ʯ|O߉eJ#s.!Ȥ>pW ``t# ĵ)MBO%ģs{ᄙzޱEϽa 3 m[l1c3$٣m X]a]w6kwaCPr .) RiȜK?2){ji pK.:|m$lxS+a> ԞA}ϩ)xQ J#O 0[\HxJ.ӹ)-ٰ m[q}JLlkI.vٝ.\XL GN,shJȿ-y@FS~:-?%J)4L}8,ZoXH,5{SY2&mFF[֒\]̝ܝximݒ˷_c:ܰ 55o%_BM oh& WΪ{붻Rkiv{򙥩ՇMJi(V .}6d(Ӷ?<s78~72V2x}uR>{Ұ2nglVW7)^Zk)mCה!X9?Z uS)4u~hSh2q,N_*Y?=?81)a-e-f7§/9Ⱦ {4`S,& n޺}{Rj|M÷Mo}U4~thzC[OΧhL%B?32)9뙸\^ 5PtK |M|Qd0YXKruwEJ{8&% ҫh>}3H` 0p{QɓsQ7&>;&;E% bv.%Y;; (SRhF֒ f1ev8e=An_ξJl@Kmtկsjj}9G*OƤ.Dϩh, VO $g._|c+ĉ 'Gҍ  ɧ*.٬)+qI\Z :,06GaUpWޒz;%Ozy2:Y# ϙYgXWxv+ŧ!ˏ>S5KXKrunl$揆穔0WXNڹ{Mo޺+-V *~oU`ZmcbO5} wk+֗g藲O!~8Y,yGXԩLM/@-o~6\x6v+Rc-~V|?/ᛷM[OOD{KBhv-J _@SOT+ͨٵ-J k 6O`Z*jҌ7~[J5j|j}Շ_ ׍z|>?<^ 5 77uΚ SGt{,5//\x6v+R:VZYÏg?pp?qi ^ ooC=V\+E`^piү p/~XC40 mӶuXݧ@k{).V۹;h\x6v;wN?ѭ'Χ 6O`Z*z~5L,_Su~pߓ,Mq8xz| `C[mVM[7o ~mwV9ÔsSڊmc(R7÷M^hկ%. g| `C[mŻ>L鬺u3~P)@ mӶXn1?Ժ:|u?qi pK\]{:K;,NAju Sڊm3 o)i=~,Sڊm-tu~#K,}`F0`}p>hp\x6I|f]2'u|߮C8848.VoȀpԯp>hp\x6UK8U2Y69| `C[m~/?՚p~؂SOJ|>?<> Š5EB77uΚ SGt{-5EBlh+MυsJjM87_1sLJmkā)[{|iS:vZ:kkٵ(-PUݺfԙ<Ӿ9H3jv-DXo`C[m6: (RsXo~}3臨ʠ9|s S4%K-sM+Z//sil}5'J_Ӹ Yԯf<8w?woq|)ߝ:s!8xM᭽XӋ:q-M_u[c£Z8@{ڹ[y6۱n~ 6wX-sil@ŠPa;p>}O_~WMv~F[~\ݬ}OOXpվR*|,P8g>Ԧ/OOqoU4)~<]&G{G *No h\}"֞-!pAPUЕ.؀iKP| >) &;jydq8q9d=ۿ&4{_Pu ʢGÔZPW:9r _ .ϕ?u37Y /N>;A4UhE~W*]-Ӗ&<*rh~=SNXuUv+j\%Nν c uӊU)&-0F:=^]FΖNXV|,%ӾKi] S?GOCQ6!w J 6%yp=T:4#'퐻|Yx7W4KTwo98 x4=<+GFS&/wѥ@Xfb;?ߺJ7m'vbJ&0Kov6kw"xƗIa|O߉eJ#s.!Ȥ>~/0Vԕ΍N>pN/(B)DPrL<>N;{y2<{Öf\ڶ6cfYzڏf-Bbuu%oW٬)"3 $ހ\v9E=cJtگ42Lq/rB+;R hI0\Χ CxN OK"MPg/}IYBSr?ǧ5MnɆ_^hۊH|Pdb^Kruw6v%9|>:wb#EVB%Դ`0:i+>gfm7,$-7%c .xf +*%ۙ;;eORۦ飻%goAb3tx 5+Hp^&xp=T:OEOR?=>sS_y OӶ_I{Ұ2nglVW7)^Zk)S؆%Z[0oL y M)4%]>eY0O6`S,&0\ΧOϩjt[ #nd>Kp%󙸰%~8qgrkIuCa#suY3wE%WTe..7>$ y0 8Uj*l].y^'5< uz%O>}gϽR|爰}O1]}$WWvfNb]Pjihx*zJI.M>',6N>GOР}|WpV 6%yp=p>ESxk>~VA *|evҵsn߼uWZU mӖ&)ŒwԩX MB bgڊ-LS4Ѕ!]yеss;uOT+ͨٵ-J k 6O[Χh:KqÃ? šQk! HzsSyO0uM/N8hFͮ lh+0\Olh+0\Olh+0\Olh+0\Olh+0\Olh+0\Olh+0\Olh+0\Olh+0\Olh+0\Olh+0\Olh+0\Olh+0\Olh+0\Olh+0\Olh+0\Olh+0\Ot9kޓc&Lq~}\/ͨٵ- @?piKMk)|w̕}>;sfZj]5S lh+0\O,9uIR0 mӖ&)BݺؼuWZО) 6O[:O~ӗ;Uӯ]ߩ㾻jiW}7kL>'|ǺS8}mzM *P8g>Ԧ/OOq])f|,PO1u`-LCiႠ5X_X7=;vj =^0kkSgOPܯĠ6Ai :&UrO1O- Mn[V|gFxt$O[JS]9l \#VunoO\0 p8\k]7?ݟb,sΟb*]-Ӗ&<gvgc*n'JU1ۺiES~^Sz#Z.k#}gKw'BJ H>Tf #3tx 5+O1RY?T`Z-LCA38~-ϗfJ-<GSra=ge=ȰhI7\Da|*(y֢"I OygΎO-0kgvG*밊x:ݓ99APҟ3v۝i;̑Rid%4QVM;ZVwԕ΍N>pN/(B)DPrL<>N;{Y4Q<0*жa36C~4{ma++yfN Xx(xJrveX`tگ42L O1RY?T`Z-LC=SS`RH>sG)Kę~Z/ O\~:4%i[Rm+n"%Z˸yv',䰋/ ,8 GN,shJȿ@ѩ?o(0e934nha!n9Ͻ,opFS6# UXiUa-e){6M-G߾Jtx 5+ iKP|? e>Ja|PmROSf*=wJ؟ӗ}1+g㕆$Wq;{gvG4I^w?=MZ4 A:?ͣYJNa98}a(yH''Ӑ7[>V J$Wq;sg3w 'v1͉@ Ӗ&4ɼD#YU?qSf%ŏoh-/7,x˛ h@0\ΧzԟI<i?2,zZ?2̒=|!Y"MLLY.[ZX~! 7Y1aע!֒\];;uC饕,r|ѣP\IcS2}N_Lm-\;-y^'ӝ5< uz%O>}gϽR|爰}O1]}$WWvfNb]Pjihx*z*Xo~5Sgzt$O[Χh ];w[~jZx mӖ&)ś:u G~jY?piKMk)|wL]Ri߁+j5Ei h.Ve````````h/iKGeТ'On:v=c;a3f̑#G|ر[o}~|'SLae+Y| /ݻwW\ H{gϞ7o}עSh``xO\/zT~C:ujҥW_}*6ejFMo!C4Rwtt(w`ݗ_~+oغԑ?3fCmOQȑ#/>@#h```xOXԿp:.[95k֠A㎵kΝ; /8Ѧԣ:MujYD,RXj˗RUbR<F݅ _5Uj*jJ{WXen7Y| /֖;3f̸ˆ }v=JT O6--]TXhmJ=M}ꪩS~R5f-We!%|%\=}&D,6@n{7],>3% .[Ҷö8h`߿&d5?1T'v2;mʔo|nvZ_BRkO=Ze9F5MY={~ _XيnJӪsFM>UzFz[zQ=j?A2رcZW^)eС?,e+-z-P./TZ1P¶c7OAG?xf)`ԩS۷o~iKO!i60.>%y4@Xg/&E:xIA1S p}9x4T.XӨFW+!=|#m>>O!0 6il`lK N4p ilRlXX `'Ay4@>O!p 6 tR \s<~ qm>>O XT[ZJ`X*U04.O||fC`ڃm>>O!p)% `Eo. &<&f@%W~+}X>Oiب:;;ouƌO˴Fkɓ'_xᅚϿ[̙3Gyy4Jl5ZN6/5zضc84p2 [N{{ウfR'?R-g R3F{}5jTWWW|ԩٳg@i6Vbi^'` ܳӧOu]C ٵkI K/?~}TYXh`45O||fK7$M:.Q *wyo>?|XS{}kcǎ,gΜyWjM4O>Q ̜9SG;X.3fv*{G~߸Boݺuر+bƍV裏jZ^8o޼'Nh|7xcȑzT_was0jm#^y<{%?.}V@uo~>O,ڔ8C84p}Ж-[rS /U0\{-/;sҥF]LM 7 .PE;8J)S'-J_o߮n;w/eyUd}5X-kƏl2]wv6?|M7ӧkKnVw͛7k!]vYHNV#W]k.m뫾+CIy4J4Xt5WTb^ ڵk-ܢS*TSxɌ&X8qɓ'mzbO?эw}_igW_u;X^~mKYH7mڤZ}ݧ^Ϝ9:s߾}W]u2Ӷ_Wݫl! ݻwkKNym΋.>|X+l.ۯL40.qy ܠv۶m 5k~¶l٢w˧2DMңF^n%Z^~R2֮L\RW_U mXr#m.mvA;b7n\xx=ZfV!jlsC=y hCQ4EkYƗmJ* Jl5mڴ/x:zXdC:|ǪkM9zRzIQ4JZ.KP3gܹsuWꫯ a#m:tHiʏ>GѷCl`Mе<ͦ<%l87J-dGZ9`K. /Nz/ݻ/[n%l:vWf?~|X``/u:u; n:OF4m\P^~&7oJ~vWh]J$-pHs;::w6q=F/ۇ9r7Gژ@QhRV9<&gKrm8˳?|7+#'N QXl!X:drΜ9zTYrڵkXeZ8j(-|/IFaaGJD}_.2MY^~NGm 7/cy XQ֭S:ʰ+R^ҥK/(>YSNQvmc>CBm1}/46+УFz,`i95Ed^zSZwyǺZo :m֭[{#c=c:s̰=@+tmn>O9,X,EphbN6Г;w~+_-6'٤WTVlj~7F]3vy-]G̙3oּg@lsy iӦ &,[lʕw 4rC@[i6>3WAK.+ `)6ph`=oY_z3g>O ޫJm+04O||fCޫ~ Ih`S&V<&MVZ/ 6 hk_ zXJig7p}9x4oߨ~?۷04(O||fK@;i6$+p5` D L@/x48==DcS U7[ի04(O||f;0l!-{4C6xFl.`oԘkm>>Omh`C@i6MFYZ=\X}9x4d%~&il:7_gip06$XYjRKTS[J_!Ay4s ,K8;il4{9+ rg?@<'`y,WSdo.]Z6$س34fШN _!_|%6J^[5ph`?@<Jӳ34Z_IVW~i6"yV,oʟU[mp]Сx}ilr+9X K@Si6,S%wAr{<ͦR{'`eo `h>O͘h8UVXR uʪp `O||f[OKQS_ ̗,6s ``<ͦ~:4ldl+/4idTW`)6 O||f?g!Ay4sb R,ښJ~x4UuZV63U^ *,ċ =P3O||f˿bejX{xW28ϻ84p\0m>>Ogb 'Ŗ Jp O||f `%g`YZ cT!@@i6`Y ,޾`IpwA[p+$v<7fNJ6Y?zzWj`?@<7ش կxxFJ8ֽ 6xF؂4UbMjsJ2[S`Oph` 192|o>9r;ٳG;m>>OXud+84py'_%C7qoذa=G}wtwwO>O˿˖-#sih>K.\ֻk׮aÆ]xCiJ,40lsyկbTyWԭRh+p^|EuvvꮲVݲe~N]+Xz,zO? *?iӮ:\>ѡ۲wޯ~UXh`Y4 D5̷@x=i>cq_-Jƍ )r [=}]wݥ>t=T>q9qv[h4Q4`9C/B/_"37_^cl!/42P39sFSuΜ9@)gJ-HOI_Eal~WO ‹elj+VU^]4K[h2%[vAŸ\2Nھ}; 4 O||fI `ExYJ,>5`Ν&MҷL{=C 4!O||fϒ `,Z죰*J L <λ 'O>@i6޾|xo}ZxŊRkil<sx` |WT <_rU^~۷_lqVR%L@/x4ߞZU]쩁dil++^$W,P|\:8y4d^x_65'> 8ϋil~zS?#h_go_5[/8E`ߜg 86X O||fc+֞W,QXկ2RJ[xrX il~g^}ZoEE`?@<&~WNX [~840 il՛[%ŗӻ `m>>Og\ϪߌRlDmJNoBri6 To>J<ե+,Ԫ/W 6Xf^R)Cп>O̗WX^Uq~$!"DE0BCa`Q $iK_C@J4=pnnDEMLC# /a3kιk8{q5ǘc<=sYqB!Q 8u.`jBW^v6ԍݧu[ `(0 lۦmYmo˿ p.BoǗ*w;333333J4S7-mJ6/T00}s 333333J4S7/2HY,K6/40` NBx6pऋq,6Mۛu&^b&j\G9E;@iFcPY-/}/? KE༁ffffff}M1us//(VM*+jV708o`%Pڦјi[J^/BOcG8#ģׁܹжu~ffffff@iFcPX:i&x1+8กu~ffffff@iFcF՛ar2?+^UW60m>\Ymo&_`XqI~i!+n`33333>PڦјQy:[\Xۮ~aNi`-!"08o`%PڦјQvx3Ծ7 `jo*1 pG 333333J4S7ƛj>}0p5km<Ym̈́f7gjO 8"p lfffffv/i4nXߝ;w* 70 333333J4S7O½pQ6̬ϔi4n: `kM"G81!n`%Pڦјi[&E]/}.0E` {r7༁u~ffffff@iFc Fj@/{I/IYYlfffff_i4nXLoZoi܇Ym~_P6 = nf pcruDiFcm p3)A50,) ?衇+m[M\resν}W6Qڦј ~ `Д nQ6ίҳ>rȰaúںuĉd{.!֮]SO|ڵkׯ=z4C?꯿:A#F8s挶3wYfͶmffffHiFcFHٯ ur#={+8_mݧ~ԩSW^ͷ˗hΥK.ZhРA|w=}֭UVat-[ƣ7hugܸq+VlӦM/s={v֬Y?C<{﹁,QO&ӘQFyBe72iP`jߌ)pbj>0^#G*޵K,y7mڔo߾|r<=H]vgy饗G};O̱H8|KϠA,]TS7ޜ3@ŻGϙ3gʔ)|̙3'D|5}tz֭<0sĉ۷o_t 2M'oHnx5p";vpPpȑ|OY`Alsڵ>| BM :sB|<[p녕N0 Gx ]ȼ~:6cc| >QEx3g\]z}޼yF_.mEPG3oܸ1sLtKc7q^{ g͛o,.cmB&o`!}~Ae)e,|^\$Y KWb~t{,ۏI6Q=w<;olosΝfkffff_4nbS O j]P  H<67m]t)7%KB!A5#_ŋΏ?;#p{8V!Xbv{Qw>I`_7W^j0tbD oߎC-9nظqĉ1-k/VE>,7,0jժUXIc=?kx#^u 9x n394eȐ!8iӦ@x{1axY3Ï f?Rtm2o_`F}"6h[w`\ Rx X*nݺO?T+u:t͛ w5 PƋ=z4&Çc g޶mX3N 'px16<;w.ި<4UQX݀ųxbW-84:nL1u. iUvs _P(yKj+m*t޼yȼ"Ə"ca~Asa|sׯ aJcP%iŪ|M[9;u~/T(yK\~}ԩWn~:mڵX~@<rϟ?w~w&3333?i:03%6ip /  ౹ ܇YW'wuuiZzLFqm6P6s $hd Ծ-o~Vmx$k%JF:?{mffff/UoFf4nЧ@v3 ](0(yKT%PFԾ0{X(Sjݻwo0x\J(U* ߌ(mU/hLݰ1ٛ-C*S/z3jߠ=0FsTߌ7333333J4S7 ۳@ua7 LU.4lfffff mEf~=K ߌ7ػwoCk/\9/_u_jdJ4S7lL`0E7xT 2oڍP633333PڦјiQ"0}AQfԾ74bNMل 847P*`33333(mhLݴ_r4PvR 4q `R@[Egffffff i4n%Oh 7(|3M_ o-Ymn#T*4PfԮʿW `@0)oFYm%oDQJ֌j6G #С @Qft~ffffff@iFcF՛Qvfb5 ^ :`oͨ}oFgffffff i4n5gͨTElF4}zdvyIENDB`

Docs  /  NCRC Recurring Contracts  /  Working With The App  /  Dimensions
 Dimensions in Contract

For line-level actions that cause the Payment Plan to be regenerated, dimension value changes can be entered directly in the associated input mask. To do this, Change Dimensions must be activated. The dimension fields defined in the NCRC Recurring Contracts Setup will then be displayed and can be filled. Dimension values are only visible in the Contract Payment Plan card via Related > Contract > Active Payment Plan.

Docs  /  NCRC Recurring Contracts  /  Working With The App  /  Payment Plan
 Working With Payment Plan

The Payment Plan defines when and how much will be invoiced. It is clearly assigned to a Contract line. The active Payment Plan for the respective Contract line is displayed directly below the Contract line or can be reached via Related > Payment Plan. The Payment Plan is built for the entire Contract line period (start date - end date) based on the Contract line details (Quantity, Unit Price, Billing Period). The first Payment Plan is created at initial activation (Active status per NCRC Recurring Contracts Setup). In case the values of the Contract line change or another action is executed which influences the Payment Plan, a new Payment Plan version will be created and activated. Example 1: monthly billing Example 2: half-yearly billing Example 3: yearly billing For more information, see Working With The App, Payment Plan, Payment Plan and Start of Period.

Docs  /  NCRC Recurring Contracts  /  Working With The App  /  Payment Plan
 Payment Plan and Start of Period

The default Day of Period Start is defined in the NCRC Recurring Contracts setup and is transferred from there to the Contract header and thus also to the Contract lines. Day of Period Start = 1 means that, regardless of the start date of the Contract line, invoicing is always from 01 to the following 01. Started periods will be partially invoiced. Set Day of Period Start to Starting Date defines whether the start date of the period should be automatically adjusted to the start date for Contract lines with a different start date.

Example Day of Period Start: 01

Billing interval: 1M (no different start of period set in billing interval) Price per period: 100 € Start date in the Contract line: 05.01.2023 End date in the Contract line: 04.01.2024

Important

Only complete periods can be charged in a Contract period, i.e. the first partial period and the last partial period must result in a complete period.

Result:

In the Payment Plan, 13 periods are created, with the first period having a term from 05.01.2023 to 31.01.2023 (period start 01). Subsequently, all complete periods are invoiced, whereby these always start on day 1. The last period is again not a complete period. The price is calculated as follows. price per period – value of the first partial period = value of the last partial period 100 – 90 = 10

Example Day of Period Start: 15, deviating Contract period

Billing interval: 1M (Different start of period set in billing interval) Price per period: 100 € Start date in the Contract line: 01.01.2023 End date in the Contract line: 31.12.2023

Important

Only complete periods can be charged in a Contract period, i.e. the first partial period and the last partial period must result in a complete period.

Result

In the Payment Plan, 13 periods are created, with the first period having a term from 01.01.2023 to 14.01.2023 (period start 15). Subsequently, all complete periods are invoiced, whereby these always start on day 15. The last period is again not a complete period. The price is calculated as follows. price per period – value of the first partial period = value of the last partial period 100 – 46,67 = 53,33

Example Day of Period Start: 05, identical Contract period

Billing interval: 1M (Different start of period set in billing interval) Price per period: 100 € Start date in the Contract line: 05.01.2023 End date in the Contract line: 04.01.2024

Important

Only complete periods can be charged in a Contract period, i.e. the first partial period and the last partial period must result in a complete period.

Result

In the Payment Plan 12 periods are created and all periods are identical.

Docs  /  NCRC Recurring Contracts  /  Working With The App  /  One-Time Payment
 Working With One-Time Payments

To process one-off contract components, lines can be marked as one-time payments which result in the line being marked as completed as soon as the sales invoice has been posted.

Creation of one-time payments

To invoice a line once, the corresponding field must be ticked. This can be set either directly in the line or in the line details in the One-time payment area. When activated, the content of the following fields is removed:
  • billing type
  • starting date
  • extension
  • extension type
  • cancellation
  • cancellation type
One-time payments are invoicing using the existing invoicing functions. For more information, see Working With The App, Billing, Customer Contract. In contrast to recurring contract lines, one-time contract lines do not have an associated payment plan. Created sales invoices are displayed in the line details in the Invoice no. or posted invoice no. field. In addition, one-time payments do not receive an automatic comment in the associated invoice line. When posting the associated invoice, the one-time payment line is automatically marked as completed.

Docs  /  NCRC Recurring Contracts  /  Working With The App  /  Indexing
 Indexing Setup

In the Contract setup in the Indexing tab, an index status must be entered, as well as the rounding precision. It is recommended to enter 0.01 for the rounding precision to avoid error messages. In the index list, index codes are entered, which are then also assigned to a Contract, or a Contract line. Index values can be entered for each index code. For more information, see Working With The App, Indexing, Working With Indexing.

Docs  /  NCRC Recurring Contracts  /  Working With The App  /  Indexing
 Working With Indexing

The index fields must be maintained in the Contract header or Contract line, and the index values must be maintained in the corresponding index code in the starting month and year and in the comparison month and year: Indexing can be performed for one Contract line, one Contract or several or all Contracts. To do this, click Actions > Indexing. After the indexing has been performed, the new prices are transferred directly to the Contract line. Via the indexing log, which can be found under Related > History > Indexing Log, the calculated values can be printed. There is an additional option to inform Customers about the index adjustment via an additional text in the sales invoice. Set Printed is then set in the indexing log. After the indexing has been performed successfully, the new index values (month/year) are adjusted in the Contract line. At the Contract header the original values remain. For more information, see Working With The App, Indexing, Working With Retrospective Indexing.

Docs  /  NCRC Recurring Contracts  /  Working With The App  /  Indexing
 Working With Retrospective Indexing

Docs  /  NCRC Recurring Contracts  /  Working With The App  /  Cancellation
 Working With Cancellation

Cancellation of a Contract or a Contract line takes place at the customer's request and must happen within deadlines defined at the Contract header. The period is defined by the values from the Cancellation Type & Cancellation Allowed fields.

Example 1:

Cancellation Period: 1M Allowed Cancellation: Till end of contract Thus, the termination must be submitted no later than 1 month before the end date of the Contract or Contract line to be valid.

Example 2:

Cancellation Period: 1M Allowed Cancellation: Till end of a year The cancellation must be submitted at least 1 month before the end of the year, i.e. 30.11.XX, in order to be valid.

Example 3:

Cancellation Period: - Allowed Cancellation: Till end of the month The notice of cancellation can thus be submitted monthly. In case of the cancellation periods, which have a reference to the current date (Till end of a year, Till end year quarter, Till end of the month), there is an additional task queue item, which updates the date. For day-accurate calculation of the allowed cancellation date, the Job queue entry should be run daily. If a cancellation is not submitted in time, the Contract may be automatically extended. For more information, see Working With The App, Extension, Working With Auto. Extension. When a cancellation is entered into the system, the cancellation status defined in the NCRC Recurring Contracts Setup is set. The status must have the "Billable" boolean enabled, as invoices can still be created from a terminated Contract. A cancellation can be executed either for a Contract line only or for an entire Contract.

Cancelling a Contract line

If only one line is cancelled, but the Contract remains valid, the line action can be executed under Functions > Cancel Contract Line. Only Contract lines that are marked as Billable can be cancelled. For more information, see NCRC Contract Status. An input mask then opens, which is preset with values from the associated Contract line

Options

Cancellation Reasonselection of a predefined cancellation reason in the NCRC Cancellation Reason table.
Cancellation DateThe calculated date based on the entry of the "Allowed Cancellation" field (Contract end date, year-end date, quarter end date, month end date).
Latest Allowed Cancellation DateThe calculated date based on the entry of the "Allowed Cancellation" field (Contract end date, year-end date, quarter end date, month end date) minus the cancellation period.
Cancellation Received AtThe Business Central work date
Upon successful execution of the cancellation, the following will be executed:
  • The status changes to the defined cancellation status
  • The Contract line is no longer marked as to be extended
  • The recorded cancellation values are recorded in the Contract line

Important

The cancellation has NO effect on the end date of the Contract line. If the end date is to be brought forward by the cancellation, this must happen manually.
Once the Contract line is ended (no more non-invoiced Payment Plan lines), the Contract line is automatically cancelled. For more information, see Working With The App, End Contract, Working With Auto. Ending.

Cancel entire Contract

In case an entire Contract is cancelled, the action can be executed at the Contract header under Actions > Cancel Contract. Only Contract lines that are marked as billable can be cancelled. For more information, see NCRC Contract Status. The same input mask opens as for the cancellation on line level. This will be filled with values from the Contract lines, if they are identical. If the cancellation date and consequently also the latest permissible cancellation date in the affected Contract lines are different, no default values are displayed. The entry of the cancellation data is identical to the cancellation at line level. Only those Contract lines are then marked as cancelled for which the cancellation was received before the deadline.

Revoke Cancellation

To reverse a cancellation, only the status must be changed. The recorded cancellation values are then automatically deleted.

Docs  /  NCRC Recurring Contracts  /  Working With The App  /  Extension
 Working With Manual Extension

Contracts can be extended by a defined interval. To do this, check the Extension box in the Contract line and define the extension type. Extension Types/Periods are maintained in the Contract Periods table. For more information, see NCRC Contract Periods. It is also possible to enter the extension type at the Contract type. The defined extension type is then automatically set in all Contract lines. This interval is then used to calculate the new end date of the Contract line. Contracts can be extended under Actions > Extend Contract. Then - independent of the time of the execution of this function - the end date of all Contract lines will be set back by the respective defined interval and a new Payment Plan will be created. The status of the Contract line briefly changes to the Extension status defined in the NCRC Recurring Contracts Setup. The status change can then be tracked at header and line level under History > Status Change Log. The Payment Plan will then use the price and quantity of the original last Payment Plan line for all newly created Payment Plan lines.

Docs  /  NCRC Recurring Contracts  /  Working With The App  /  Extension
 Working With Auto. Extension

PNG  IHDR@JsRGBgAMA a pHYsodOIDATx^ ՙ {z~_I2L~$d 3t|!ncw;2mmbs2n,l $a"a$YB7U]8$+I $!ݎG:S}kժUk}jzQU{UڗOK!B!`B!B!B!BH)&B!R h !B!`B!B!B!BH)&B!RD>^tEcƌYzuww'|#8W5]fh !B!/| ƍ;p3 tsqmq4H)Y@L!B!@ 2dΝW+=@L!B!|s[tC=@zGա&B!l۶Ê+P޿?}B -[n6ݯB^=0 0!B! fڵű˖-7nR`.]Z%Nh !Bi05k֦MN&Nm6y ̙]9+V%$O/ݼ{3g  Qͅ D.Ell85"p 2w>'A ?\0jEO>)?Oz:igm =qB!RN`5b_aG.LU`ZDFyWݼEJdg(SJCbdžjsS:un瓳=;\7@_jVr7vu ;C::6/SKkr9uL;wN>PN{%٥ƬG'mOsg,2E !BoНlxOaGM 46#ŶdylcE@d3g2'qr]=]g SwMWtZ15K`zzN῞#P_i<1+;^{Ÿwt~k5E0rewϮ߽i֖ٿɹ:(J[maa ұyۚy«I7vLB!ҾwyXF:thժUk֬9x8p@wJC~J%g7=٬mo:;m;"?9mml8eegYٮr0|wN!gm >a^w ^ݞҗB!I/ݻG?ɟ ??DZc#i|W嵻 n#GJi#%^¿ؕ\mŔͧ6Lqfn ߋ4Ƭ^ܱѺ4Ƭھs-E~Ngw׶mzԶ~\.1c42u'N p׆y̛pŶ.cVlFd|VYcgvl De޾0pk捿w9g{G@S9ט5^lWo1޳Xk}}ӵ 0!Bj`ɒ%wqu]裏Xk{]`!`Ċ5 Lx2΅U[u$`׏p/G4.1kmW 5zF4\x:1'ssFFȊV >.c"0MlB!$+_W>^{m޽.6Ν;{=l`M/~QfŝLNmX,;?1k{kxֶr0ms3G\?l#p+]=[g!_ј*W1{I$؍`{E@4;qj0ٷ_13e?/S6=8wSԛ:dWL)kӹ,Y'8١.]h^:۽y7{{'H\?mEgXRq1HJpŨŝg?^3^=~o۬@ӥ!W bUl߉kqPo'|d6t,8yfo>ӽQRף{=ӐsIF)*Uiv+oq׊=(4XB!w_vek֬۰{nv {I$}fwGw<54ۼ"nqٱ˚}Nwb` o?^4;qjy|W~?rž)]1eCwO?bͣNcG @|8Fcr`VvG~g;=aHf?zBG'<ӵyֽoN2cF'o?[?o°O_p')+l=]⽱5:1s:sŤ˫霐5nJ6;۹믿w޶]Nb;;l 6oyh%qSJ~YG%tV>oLNdxD ƎJ?қG=F8N22:Bsl;s|xbs:8oѳ ?9sάg]T`:G? -Ɏ$9@P˄?B+;L!{SJ<ڀޓ)*V)؉t &BH/ *|_֤ Hmsу=csWOnfegoa˺z- xOCb+y9^q$-aL_|6miMS€tl>գM3EI[0CNZ)o=Q3ڎ# x+yxsb+`y͏mfƂ9RmE3a>SCJT`'iA2քB!y嗿~t1| .Ccܯy GXmmW`78Kfvٶcf} 䝋;EVhg=s;6`#?1ھ/!ilLX'&'*|f{{7ΫT0ix /=7ɫ6u'jcN~{%l\l/- pq휇`_?8Tc%VݛfO=al)ZT3ƚB!/,|͟'yl`w?g$k,"'\#N}ҽk4HA~) mUZO `YR| 5*2>Оwh~Nj~ɜ{pƞ(|79K4tG?ٔT>& ={Zc13(:agmwk?$U]=/3<;opY?K`ֹ' ifzVLGҢ['<|sV,iPI;ke`SJٱma_G/ L{{4OOh\P6]~URIgsf =XB!TbС/__?ػwӧW^f,; /z뭚! ] ?ۛqmڴi۶m⊪߇,gΜt#urM8q֣i85U+F c۩X̑yg؊.=6/4nm]M4H6ʿ5uȕB47wL|c?u#晷(\)_+b{ǔەA(4 {ϊ)GnHX-֟t_|XZt ZY T24BiϑO,m\9%Ruy3c!,H;E*3Ց0ƚB! ,eOO;  ®7;wl'\n]"}AmKo™{gWzx^Ύ 7_ݹdtnɮyf~kxkAY ( eN><+b++.oe@ 0_[B!|۷D Nݻwc~IExQ3g ^"5l },>SJl gJewĉWJFrpȑ׫HR>N'u@R%$F5r$ A ;~"cM!oc ڼdMi سA?xbiȐrP$(`UŸ $xGqϖ)# !B|_=}k@|+- |ga&acĮWqD'9sXߵkA ʶ@wLe`nad,~5n-[dȋrmHd<ߖ_)G K>;wN>PJӝmjb?q~;B!ܜwye5[Ĭb1XGʆXftRke(Xl[Z*IR3gX.@[JjILjgȐ!= J$]B!RpjvttGoYM mp6w ,H`#R$beɤ2 KEk/U) {qjEHuvݩ 0!B!>#zVӾ 0HcFEiAJ#/I9ȅ8. 0HPMݖ,,5U f>mٲ>\i !Bi{ƅ?'zc'^`.]Z{zuB! `X s, =@L!B!X| _7n܁f̘1hР?__lUIh !B!~]tј1cV^68^t&B!R h !B!`B!B!B!BH)&B!R h !B!`B!B!SKYTW^Ëq>!B!BQiXGAMl2˗PXOs=ננ7DoB!B1 Qנf5D}Wk#eTiXA]o^m!B!bP3DA-kY f ѓ!x5M#B!B zu 5 Qj+7Z|*~즡#B!B jyx55}5 Q3ZpTEAAn>B!B!ϊMvԠzOi%KPX_J~}3|W&B!Y#  dž QkPkdu :4m!B!b zUk OFf-/ 9%zXAnji !B!QYYAo_F6-) rb1j|CQ#B!B j2C{z;  ZRSȣe!Ru5i B!B!78$jS bzf95?z_z}B!B5@:ՐT ,4k@N&0<'Om;~c"lUMG!0tΙރSc l` &۰&%BHi)~S nE\ZV:oVkH7RC-: /G|u54HBv|ѨїΞ?ik;>:|4vq/!!f#BH 7oLq@.UոWC,%JrVj5 &0_L KBi9~fX\]=Z$u$FdԣBVYV5`wھ8ifj)BZwݽ5̨uB!1NSPAVu-7R*ﵨߍ~7x=O[PE!%K8e}_#Ȉ(D !OQۈ7BuPj)Q$RZ^5 }5ٯ+>&f>‹(Bߨ5lźb896~ZzC&P ˗/_d}pyBH >oN+BB!qSh<_Cd%gR'5!w5,[|s}Oj֫Bi^hBi*w$( ;!gQWu֐j_k%T/*נ~7_/^}:9To$Bi~Q+VN{k(Vw!ҿ o jJ+x`'+V#,=A|1~a<]+Kz+ ejBm;>3qdO>ypl}VV^ݧڪ;]Ǐzqq~a}BH-jsou~_NR`5_g~AMw~xv/'|yפ>xud=!ǟ޽/?ȡ?zg^ݩ9LZz>G..>rмbo:o?uSzyhBi7>S?qfU?9zG9QEO<3v~YPӠ4Ç U !Qq M~>f%R]Eǻun2?N~x5|͙ؓO?[:^zCa~Ι3gNs/Z?~Uj~l'lw_7D=VTxU:X` WhNe~ ?<)ϸB(YA !u.=_w2 k3?zg_:EK/5E쯃>r5Fo<7zb=V٫{OH~ʩO;}\./]opW<3?M@5j; jPSà~} f?j|8)_p Ѻ7'ywמ_vcu>{`P>(sb1{luqԬ6# z_Y -Е|&$ff CImصpeڌϿRcb[l뫯dž],8bP _[&-*C!u7`~ )t9XKl?sO9v }g*_ T]UYj`u$jM< {C'{Cĉ~ pC<__z_CmX/PkPkPkPlE0$oYw~ܹgn`Bv/Yb ɶ]e*pv]*XoW>\n=t$Oa]_`/z$駟/uuנ7Wܢ: pϾj{ `%L-F`>.tn#`9.pu8"%`ۿl&S."&kW VBJ~ 4!!L\+N۶_Ԝk}a_'۠;;qƬ֊izXП4'_}m}g25UgkZ)ɗ`dXh 88~AMwҥK.}=.֗_I!hJ߃u /~GƼÇ3hfP, e}rq}zYG͡@!oںom pk<`@ˋ3R!`0`ھZ8Jr !4o?TwAa҆QB!!lk0Zz_zʏmm_uU?Bv|fi((!Bj[82ZR#~Q-ߺ 0{}*eBi&~W; bԊU|K!W 0PkP`)xtq@*!Xנ7~.<_BiwU=ZAQ(>!Bj P1bWj3 $ z4 3gjN,~ !L\g&N9||D!( >!B}C܇@8VuyK~+s[P1} j 6#HYl0 %B_xK遑('BHDoXNiu=> nФNu<ھFṗ?) cGpj:B!}g&NȈtBH穧kq 0Ƶ7נX9Hr&9E/Pk~BH9?Q+V~f^2τBH *7m!Ұз3LG?L2F~!Rf͚ի`C 0N/UXAoǿ@G!d,ܶ}k;|4.tAH%BJE ?N1(RV[m!Ru.wA̟ݚB!!1bHS=xXVkPk`)JHR/Pf/^#B!B O>d,T\8VqVkH7r~A~i !B!xW#`+`'!pd%sV4B!BT1W,~6CZR!Lo-B!B17O5X n.Vk~_`B!B!qr- H`q@-oq-B!B!'x3@]!x]н> fW`ULL!B!``=P3@CuV5}{s4B!B<`]γއj ,5Tr@/ 0!B!40@}l5F~1.z_h@_pԩw`ÔLSNnrRT׿={8Svuu{_<+5D(^ve{.0 +~ 6 %:+,虋.4O0 cƌAl:tH w0x!<u9> `лFr=A/jjQ~`?c3f̨a,nF_|7K@ܕu'd޽71^ u]wauV>9P-)a¯?#=dš6 YPRb#3j`Pn0X?.n" au8qĵ^{UWP-0uJ2 G\*0_r% : {s3RbR 0PqBT`1.Z|ǿǿ/}>\s>}:^OOW`ʔ)Ϝ9زe vo]?{^x?ѣGu?dƍ )SYl?~\sU3LJ#E8WJ0_W֯_aI[7põ^{ =G4u 0!X`3> uвjxº_k{un.iӦ51w~I灞ϾƎ;bY#C{t?sJop8vu9y9یȸώ]+_W8M])+U;mڴJ笴x裏^{5t?s׉?ǑԷHH /Y 06d< Nyď~s=.{W5'|co8ZwU]zE]oF;}v5d9}䥜d0x,U:В ý3vvvu]Q%<2ҋ/hyWRMgH}w1}ِS'Eb F 4 חCl728 *!~M6i"(CV/I*viyEIfYA8t^~à27pLH{94>6TH"{Rwr~_|1N!?я4XyXɀ|KIx骫BQ'ODI[_Ռ3Q;SQ_mgJ@pϻ+p N~|7xݏ㾚=%:ʳVfL<,FF^2e \s ^C!8Xk57HсU) O㑬EbfqOmF;jbq)}5mV.Hx]!_Z \$.moDC%=d׮Fu&GJs*}6 Xٵ5W0vw ?io/L2PEwAyVG $ \WF,Rҁ+{Ǐ0V6)Ē٪ih7dہV5{7zH?o*?x`ww&VJPsd\dPp.'j``iC`8bA` pǿ4 =Vɿ1}|,??>|8ܩ*c$=no.U֠we]fKPi0Xa.f`c=5<} X~='N.q@.eݏo>ljd٫{, jú~;voZ2a;QUٵ7ᚨa0x*hb;Tdhb'w `&ˮ k1 ;E@'\|L "^RTYl:u wٲeR%dPlBHoQ[* V΀rx {W_}C4UEx_`,b 8 Ȱ}v}*&L8x ݯ OXc%âw X6|wV8z$[RC+o|?p%bw^Qvĩ%~" /xtիW_veտDݏV:>DƏϙ 5uc*8;uVTo,:|;ITv؋^J%8sdDd|7=\Y>8BHNj~X 0 :K@/)R!`o,`p{~SnV׾6cƌ*5}wxoѣ<B kJv_͞*-fL0}I~Tݘ*R kq8/Y\.GHurڽ YN*`k0v1īč?} 7x SӮԷJeRiNUwD \uUcǎ]lٮ]Mf{ `«YHևBJ` fF` U =V `dh=yha=ϝ;O׆у,,~)߿Kk ݻw_|ŕ\(KeO|j:]~+)+qʼ )u?7VEc@^*,,z]>!Ioc=LxVd/_:RO-I췩W)S5 =":X0Æ s5GSAk5/#1RWHTk4J{X!`nL=6bĈ?m備)S0{(Kp"qޯFa>pU|K>RZ\ R 0PZX T7~w}YկOGdDI`BFEK)aR^yg'A3RnA~*,7nD0`xɰַUi͊\ngb(o&]WתZL\tOaG0~̮Bj0ޚJz*V*Z$os  ԹV,ԟ8HT@+##XiūfJ n?|;᪀?}5Qϯnw޷Qi )vW +Wa !{ջUXF-\B/}K',8Xno*KKB wwof$ݳk뮻n̘1)o#6ܶ8pK.A辡)?d?헿;MB^{'NC!Sےo aX01k7lݺ'? -XG?~R޵^'N.!lٲ6K 1\ wuuS<.m9a`jꏾ~cWWBU׬Yc+F6l^ލUWz7O{W{6%G,|n$ pOOڒiotȭ_`m۶x7$< !ߠ7 UWq@oF,%zB믄Ϙ1sϽ袋X^ ߵnݺɓ'[߲ wSAT_ Fu7(K/dg׿u3v؁Ұ,*6nSb/~CʵkעCRؔIT Fp Xg^:8u+O]>dǢJ10.lŊAG6n܈b~adXYg簲Dvlc1aÆoۿeP/篽3!}wb.']p׾5\O"3Hz$MTLk0C'XM0x,x 7I]|uF+Blܸq|ᇥV%e 4@~_{7Xw}]wy >CX3 -h /e7`w܉͛.ЗeġTgLdq 0@#%nrM/|믿~ ,7;! WaV+WWK+?UܛRkZ p% U2mlԩgpX!n̸gH\ wvA|ꪗ_~9i35bP7 l/BX|\s5|SqL_4!0tQrb ) ƪ&D<G<[mы/kT2VՂUɓabXAbГ`[sxi$$(٫{!C wIiBJ`xi*Ee~+&LP 0xd/Cl쉒]!tvvu]@$Q^t{eFl B~1jZ 0JE݂Ai.X{5D=Q[i@ 8c-8#LN.KDY0o@Əcƌn;,g!DqY< PDKh/cdoF B)j3`TYf$XNgT2o?3B!B_`XOeiQ `B!B!} v=pv M5~k=:_3_`B!B!3gTk.hbX1U>$"Dk6X/ 0!B!T T2@o1@  Xr__W }B!BQwA7B!BH 4B!BJA`R,Z,1B!B17-aKXܫkA7Kl=KL!B!$#j+`(])"3@̬`@L!B!mafQ`Zl- E}Ɔ[((( .50gy4jnVkH1R&B!$z5@8VKX/Rhg g`B!B!I )&"TH;s7&>8{z&m 0!B ‘O=Qim܌娾(*Xoema9t|]q´O 9zGt=>uz^Yu8WKNnkh !Ro{~on_|ʑ~ ?ՑSMR%,V wZ/l-G.w_Ϛ3_~=0韎z`45iO6욶xט 6yƲww;qrk`zEknwh !,|g=7mUa߁oLx#`3>Vۯ Xz Xo4}1ѠgM ;vo¥{Ox}|hP#Gb ty0uG\vu|/ pcȑ#^xʕ+u?7;\p~sW"t?`'&s?1ú'K>;?܇#b!N=XFc ^|X_+x?dَ]|o=Ԋ~Hi;V]"F&ɹ/~!UA^O# 2~C [|3w,\ڱٸC,tÖ]44=9 f$oFst0>(9ge_zPe:Wo`M$FN IT4ZA~wwuol% >x?]Б}'N\ qP 0cA7v?7g?h],x`;;ڰqQ.a kS/J*Dvsvodg{<)3?a͆apN N&!wtcup﫯{\ y/ `jo%G}TJ R!,_5ھ™>2;mט ؽbUBpjM%KJF y'@ce 1v%@9mʾ'G\-/ ~hF=mM,^G5uA>{%n~Uj"^crPr޶g6#䕔6H _S|TT^QTHdTIb7ncǎƍoXK׽h%Kd+'vE!dS#u.znaՆ`4 um ve_q$8[ =ni^T"GP%v5aCڎm;R花c6ʴH` ;Stuu͘u᭷|k~t|0uuKIx=nG56<=")%#HoH?H2+Në ٢0|KYb%mo#7FF/ܑ)ptȎWqp ݻD@z/-2ncv݅dcmooR:GRInٶ5FU( ܒݍ&L ĿlTIj(uH W{kbmb~+VzTxH+$^qx ۰0Gq{FW,@2Emb3ʹj([$%9[M %!ʯ=N5Onڢ;>0REˮg5jqۏ g> )3w=a3XeΓx wQU]6lKdE`FUʊm` Ȟ\s:Ng'Bn%KybV(w`naq_ՉGX a(NaeGP^Jv=b%A.YĿG&r0("4{"%w7Y{mHqPN#H`V^KۖTz v>l`0+vmWd][߲r8/f=܎AU@ ;Rm4پmfVmmS6Q^? Dە5]y[TyRakh63nr' FY#=L, z+Y*8 n^5Ex+B$ A2-^ͥV% *#Ka/%ʑW @FI6}XG#.Ɏr%q[+p@5u ؞/_l_Y 5iPDNI|Y*UJV^)سcRJNM/ @Jx}qWt'C=z8[_WM 5ZcOWgl"ʄiwKiP,TI^"x_c\y+`K[ t"?t8E d=e ւ{"F,X]Y!pl= &( l] vSVMܫ$ڒ r7[ @FrP5Q=vc-ؖz=,ւ4opԭmq/%Ƥ$H,ΩMrܖ& d)DRJӄ*HfbR&m4O^!lˣWxK.ȞjGb̵ivO'gJ@H*!dd|g-3=zk=n~G=XbQ5M>YF#/M/oMWh,AA.%O(Hƍyr,p~-07%`̈́ك.eMne/mRkj ە>]LFp"Mid_66ےl9u%,MC5mGGlWcCvwEU{RZa=p"[`[y$HK@'Av!j8Ҍ;V^®=2JT6b-RQ. 08~X j54t"|s|v%X$OC!p8;@ QRUٶ#v[@.mD}IR+ c,۶mbh;vҥ73_E]<-W0~w{d~(ׂI P2qFJ[+&Yj벟JN'`L !$LZ>=k"ΜM[xT9H?Xsh?M_ 0:.Xl]PRxi4,'8.JpDV8"ɰȈ* lpYR=KjM܃Jذ$$`%vb $kxgAصgl^`_rO$C!%I`[~H#4 GmEM>ư@W2H4?K’Lkʷb{!NJMLk*Ť=yX rI!rvl#[m.-$Omm;Yry p~j5h;4D⎈t5c݌nؾEJ$m$/$}!h'RA@8R[^(]!x>HؐJ>$.K;ж+*mb\8^$h ]6ݷ4Ty\bJ%XJ NX듳qW΂#8)rlݒX*,lU !V9|䲧ӻO7c&{|~A=jXW]&0 p.>='nYgMW鱓%ڀcOQ֝c{pJ E6WB)&{zN~Kۂ`qV,_`GK`}/qZt4??J«4m 0!B` n\{r`51A'oc#@LH&ǀգwX/ 0!TB!OPkVz6~5~lܯgqvm!`B!_cxO5!0bTV1j|C`B!B!Co`- Xw]KL!B!jC,V#N` 0z_ e&B!g&B!ҿQ,لJ0`!~B!BԩS,8aQŮ = W0 0!B!> gT3`ްq EQEQEQTp 0vA Zo &%e޽E!1&\:hFd .BZ< 0!MBHAؿhS7Gn\„o0t~?ƃ! ͆i7 a XܯgBAL! 1y+N8)p]n }SG<%~ZlhvNz`!bc<4B) ubwB駨͆i7h i:4B ys-'&LF)jmyڍ`g $1M৴}`B!`N:ɾruNX~Zlhvcʔ)4_S> *U闐 0)/4BD}WBע &͆i7kq@/@Bk p~KL 0!B)>jmy N1N5@o1`4Bʌ.(-%jm~w< 0!MBHE\Dmz=yڍ1,-ސ4kaziIAL!]5덣4O6X_!1@hg]k _`RXqōnt~5aيT#g8FHhq~AY&K?;н6 ᑠ/l7L㕉FoL fರaB ޠT  n];)-sI#!ڐ{qORZ WxO  QKL`,k}kbA +-0m!ۤe j&! Sh:.H{[L6ˌd6^qY}6ݠ&cgpU5_ ']z}cg %2XOھ i(cĄ\X%w-F&ע "rG0"N lRxN$ fuvun 3d:ݝGdQ,D+j#E\S:?1Y,( ǮpguL#>uRƶp?WӣoK@tҠQuI ^ B`̠x0ݢ0H2D&u:6dhT2Z.j]LoQ3BwE'Em64Oj< T%4u@GHH\kr Aj\_E:"iMW!Q$-aj2:%G-XL8 ];̅fMtu-Az3"}@jL`kW~QX:uz'‹s\Md[ºxI4 bRuSb$ #Kzxw6E2Di(FHKQ0q&k[dQ"Y-)]i(jmy 1@ x p&%—`YGod^ /W?;UG_MڄJ7ݴ'zCU"LD,V6N*pT2fktkFé׻3`U=x%s59*m 8 l[tHĤ\= Ūoci$Cmrp[dXT_EK^LPTt] HORZlhvcI čzS@ i{ 4%XZ+J~]{4kwɢ6D)_ծm!M.k&k_%6 KD[B pXQGΔ}YLOT3F=,T)WD,dVBL ֣ ~%Xr55**E'ըB]"vcฉ'`ziGo4D2DcMvX$G;IP}-.iN7Sk]Hʩ b!i | n#5|DƤqCT:͉@ѫm/WKb; up1ܹ)bXCɤ4n % O 1rsui)fD$s9s%,R9vqJ E|s.>jmy ~P`  0z# K-иb&Wѽw5ٽ[ ۈIE8=Z/If 8"`"ݻo D"#f;h=ɥOBYj`[ c=&;m%HAaK "A "ǖ#2AS!0F8eGaocoa!]SؘΑߜpx7l>AC Љ7vH>D]0q&;li# 4g N7l)rJ.J8 9aD(I !bfC4"=[ǽ'mPJlrk֬>|+pwm3 O;wܾ=.] 6;ۆ;v`шjA?jQ+%쓆h@m64OA\,\q>kv%{s,W>Ov=<8t0W^d}9ؤfLs.?HJxd@M1bıct'upԝ)(~K/Ixafqwqw FJRO, aV4!!?Pk nLWaW%1  /ݡ1\܃ .j7 3:k:&CUS?^K,㨇-T c{_RCn'8T,W+U/ fnQn&QyU&HVNg[ ?>fk>nk qwN7WZ5dȐìBE7^B~7Jzɠaw{ e64$Djmy bFUu]ktj eXQX7״|lЇͩAq^x+uyRtP5ǣ">y{8R~!koOJ«S!> 60ƕO> ^Z[%_S3 L.B49* u7 JimC܅Z^ &|LJ[` \Bj* \D?&5;=@{7!!?Pk nFf-Pq1 <2:[pe7ש /^RX4Y2(n`g$a jBJ0Ba0SItܐɉN 3T ]^MN%mU&!ۆ u!wuӧϜ93j( KsvYX{͛ߐ͆i7`=l hSúwW{V9#/SY闤8tqe8!HUc>-@z6]{G*Aiٝ?jT3jk%29Bg@K!uچirz[Eŀ֥>Th pa)H6]WڴiӃ>x->|4v s(,&ySzۼ ZlhvX$8ݯ?9v sw%ci )׬? UMvjWlgѿݺ?xO'SΘV3V-ļܽJ7Π{dثm\zS$=`vijr*4 $n.r?̙3Wq 8½&.X s5T n 5\OGCB6ݠ.5ܨξ7ƫ&o_VB8j52?0{N8eP=-,;|8;튅%TufƻZoal %qRF49YީadTtګɩ7RmG}۷WϞ\{qa6)8v_6$Djmy bFUk0+uZ?`#(E)81ӷgwM$ovߪDagn*VmWwb`A-i&B@h KA!Bţcǎ 6L }ikQjaCQk nL7T,y2ĹrU2`sΤAqLo rqcnaiȘktJ!fo㏇y, quFQkoK{mjmjL30&72^MNŏިU~"ڵ w=ݩoCN͛7V  q7NH.-8 >iaCB6ݠ.YnT:&?^s9>(-Do$6o͕ q+jrqCjwG7i/36ժ;5R2[ܹsW`„ k֬Ѥ5RQذaҘ4FgM􃸭mC… 즱zuW ]s+,4$Djmy b,aw?C޿?vO:%Ǐ.6dEE!ؕm~sI=/5?HJxd@&+oj)(ޑD_+ۚh`6] s9UI olr(`K8 9aEvGIJ'E6hлFr48}9؜*۠02P&pr¸+.8O-Fm64O4SN*f1!z_ p:`slR d@\Q 㶯()r< pu,۠02P&pr¸+,۠02P&pr¸-EQΔ26PK\O?N46(% B6 %0n@Ѫy3̨͆i7ӏ8? ò J M.lr G!'"P*q%L)3jmy 4!OlR d@\Q JGI8SʌZlhvC/ pA?8>,۠02P&pr¸-EQΔ26PK\O?N46(% B6 %0n@Ѫy3̨͆i7ӏ8? ò J M.lr G!'"P*q%L)3jmy 4!OlR d@\Q JGI8SʌZlhvC/ pA?8>,۠02P&pr¸-EQΔ26PK\O?N46(% B6 %0n@Ѫy3̨͆i7ӏ8? ò J M.lr G!'"P*q%L)3jmy 4!OlR d@\Q JGI8SʌZlhvCo`q@' J8t)'p~އe!\ BNEhU`c ikӏ(((*cdFm64OA\,S%aA&6m(Z8p< p?8>,۠02P&pr¸-EQΔ26ݠ.'p~އe!\ BNEhU,۠02P&pr¸-EQΔ26ݠ.'p~އe!\ BNEhU,۠02P&pr¸-EQΔ26ݠ.'p~އe!\ BNEhU,۠02P&pr¸-EQΔ26ݠ.'p~އe!\ BNEhU,۠02P&pr¸-EQΔ26ݠ.'p~އe!\ BNEhU,۠02P&pr¸-EQΔ26ݠ.'p~އe!\ BNEhUcdFeC4B7F[P:::&L !3BZB VoȌfˆi7hFSU䦮;8p+ ! 8! ;UQ͖ n H'ѡB|LO-#P͖ n h!4c͠*#3-ݠ.MihQBizq!N!^Bh12ٲy bTq"''^ z12ٲy bTt`BHgI?&'ҖȌfˆi7hFSU2;! r!?'~\t*12ٲy b#BjLf>%?p}ӭP͖ n &B!BɇzhlhvXh4B!BH>cdFeC4BB!B#3-ݠ&B!BB!BH?Gm64OAL!B!X&B!~ZlhvB!B BL!B!< 0!B!`B!B9jmy `B!B!4 0!B!sfC4B!Bh`B!B稵͆i7h !B!+4B!Qk nB!BVh !B!6ݠ&B!BB!BH?Gm64OAL!B!X&B!~ZlhvB!B BL!B!|Njĝ}mͳrM^tȌZlhٷ!~A ?;_jMڻ- Y((#3jmyZ̚gjR_x.;_u5B߽ڻ- Y((#3jmyZ̚gjUU/hN֫~{]b!ݖ,EQEQEQT}R<-3nuH 75^U~A pOF=`((]126|36 p`!z((jcdFm64On[M5D4EQEQTJ=FffC󴜺:Ol@;Pζw((CȌZlhS7#FyIyZڻ- Y[aݹh❻v]S^2 C~'ǮDE\D6,/X0uڴGdEQ%ֆqOo8lcdFm64OˁY[jFy_x;ޫm9^Rm 0ǎۃ5ogf zEb*M?d~Wl:|͂%oo٥ S?zl.ߘNX\pM_icǻq|ܹ0{Ƕ(|Zs-weԱ}ȱO w9J=FffC5ϾUkX4y_xiћ`اW dLٽs ܯ e7.Zʻ+x \iӌ+bqV鏯ڮ=_vq/!ET5 &3}kIb7[0G_xW'9om۶>rW*`w\E:a\a2|NG>G"zrcpdriI{L{tS~^c8d) 0y-wQnOb8"Z2+`{ҕ0}⤝;Փc.[{{7FJ WsKbUS3 0EQ}\^ thխ#MU*mP 0nĵ@\u-雤lUٿTܵ4'CF-\W~n n~9en;x߲'w/.OhS}tR%7]KJ^%nrkx|l˫`ab*u}gVXZ.ʘEO.z{<n3v /8|Ёc-pn{~R!p;{VQi4OqĸG1xU K^sf⡨cmy5{#l x yH^<K;^l`d.=Om~;=}i 8i4:&Kzs"f嵾5wJ%JԷiħ<\my^-G3[i)j^1k̭{g>q(_(xu^K=FffC-$\sfx5hԾ;*1v^ .sA 7kC{|d(eWG]9i$o`o:Awl_=Nؼ w6I;:kFS+>͝;VO eɣޚ7˧xEԕn pUWqOms$(N4B?W̌zmGx3*y07Eϖ<+MYfդyg;mK߻C.%/1FWK!I:LI HZ[+Qf̭6oX`Qp=Dt fM^*o]F5(>>{~ݛ~w@Rjhn.^VU|g0{}*{ko]2}u76O/PW b=jV M5 vEm6'JhT ʆNg{;,0ض*];;}+W%Kb|i=dD,my65TOFu 6 0EQ GF]<1IM ?eԻ`owcTԌohW4W]Cg=i|/M#[< p~nر(6Wa'͑l{_v? {W:tr1g{dž^ j7; Z9ւQ7ʛ;]N5ksJycddzi3FJc?, ׎= QF&2Z3L_ߓҁ5nס;?jAK_u<3vtBvVq7&ȧ>qS|fw9%0 ,z-c K8qAQz.T\UVf-O-bo: ^BUQ=o^ p䍚]Ql`ȎK]}&%Ks[z~xݺǻO`*7r>?YmJ{iJnxYӟMQT#u*^:u/*E%$0w ^ 2pZCO?{`^]3j൷V ȋ0W #GDGS~履˶7]SI?v`jun<'c] F{ ݫ;T _MtyKLQEcdFm64Oу `F]7 nR`詧ޱ?ozWM#=^6L'Oڱ{_pK􋎩@SIcjui۶X 6*EQR<?o3W(6zjGG3kn]v4Wʟt{N~]uGBa2o 5#`j웍j}nI]EQ]126 OaG^fС#F?SX)'=ēv YELQEQEcdFm64ON2 ԋh[T[((CȌZlhvXx!KQEQEQUcdFm64OA\,(((O126ݠ.^REQEQE'Qk n /d)((z̨͆i7hEQEQEQI=FffC4 Y((#3jmy b,EQEQEQT}R< pxEQEQEQ#3jmy b͆(((>ȌZlhvXx!KQEQEQUcdFm64OA\,(((O126ݠ.^REQEQE'Qk n /d)((z̨͆i7hEQEQEQI=FffC4 Y((#3jmy b,EQEQEQT}R< pB(((>ȌZlhvXx!KQEQEQUcdFm64OA\,(((O126ݠ.^REQEQE'Qk n /d)((z̨͆i7hEQEQEQI=FffC4 Y((#3jmy b,EQEQEQT}R< pB(((>ȌZlhvXx!KQEQEQUcdFm64OA\,(((O126ݠ.^REI.T4|ոvϹeصVeN`Qg ALZi 24mz*VOrU`Էq,;H5HQٮ 1޼2N+L,qi->\uo;~0U_}u*|7DcAc+ 뢝'Vl+H=FffC4 YȊn9 O i K:Vo!EUT-gMaՠn &HJ*jI:|VapqextGS"Qk n /d" !,…25s2;\עJ7DY^*c;XnQZ(w]swH;%Ңb庡Fo`]|)q?#N= CNi×HD鈸vbl%0`S pߘ8-k gncBX[XC3RzT 9|޴qYƒ!pitmC1)+&/M%/' MPHK閸bqR[$Ӧi破`?3NyZǚR< pB*;z*`{/]n`FyK"|YTlTT p CNՖSD+@&JGp,$t) O]g9H̸8 boa K QQ?IVHN/݋gQH@hcKXMrJNG4Y[-0(DXkQh#L]#3jmy b,Ud9wt tZ&>"&oi PhL'\p4aWDUW%wNn ڈ Wϼ@M6}W 9dAmJA) &7U8ꁁcW"ǭ2EQKGhka/0̝s=so8ݳc-)Ć}PU;b(\s /Qطضg* ź3`^.( _jbwd e&AIx)>(3Hć g/;vXq$~E126ݠ.^RE@[Tn Q=i˙>#%X4Dn4#Jc;'~ eۼĒSEwji$ˑhV& {R;_9 ڝAOwjD 9dtitsDi(w#Eb#V`wIFݹL`u.oa N%sDJ`{q ʹ*0k`v{p;&rI(8oJ)$'iUl RFb޹V_L1ѹ>9H=FffC4 Y([QEK0lդV126ݠ.^REQ'`&eSRJ=FffC4 Y((#3jmC:::&L0j(m=y b,EQEQEQT}R;X_ ݠ.^ȖYǎwCA((2J=Ffښgzρ5OA\,-xĿ'0MWW|PסÈ&qBoφYweɘ^PU>mC1Zæ]8b>ת_el˷kȌZ۳gIp\S7/d(gU jwEx8EQlfM3$yjG5SZ C2v%4T[? 0~RgϪMCS7/d(wUfDs`ApKjQ3auw}†=^8b"I&Gk|!r2hBM:_;?rlC v8tl4l؟71ϙm"9h}Y f^OZ;M2\AըG,tE K 9ađ&KNu/J}KxԻOk\Z]>tO}8ޤg_إ6@vA6-/ur}֍QkKL2- \?KYrܹ hͪW>}K†=^0ޚ&%5*p_r?Hնfʷ+3U-\P;M1> gҙ8[:M7t9#mջ3"jZU>WYUkU9a? ƆOצwfqqK9VPբ`^pD*`'%8+mhfSp`{;lԘQ44- "*,R]#M4-bHbEwN]aAQrVx*v] 4GN >CtyKPͮlvr_39z^w'՘(wkp\Aʠ~ A/NUeFs&IT1@wUHS AwD)S{)L )JpzR-6|LOɔ`010~.<rP%%)od jEOHvӴFI=b_2Ӆ'[4/Gf[+;ttWuԌ&v#- (~I_>~eߧwdINص=y &Ukx9͑h>~cdF- 0 pB"LhyMП ^(A1)|=W\d{GGy gQeFꌈ7J٬+- hptc{OlC?cv^ apFWG1k緸GR~i3YJKZyU rvi4 Z[A*9?%+p&ǽs5ji!'oD 8>4msѳ}d. 3T2 a: i?̵An"9y ;Pu#-Xw1{s3Q!9I!lZsK^8LUwȌZ[`lOU .nZ /Iv1pU l]oube _/f+1#LDkdѐ)6Υl3J믊3x0GwaNDn 8qgUn>3ҙa7ƣN9eF4pJ&8^ižL xI$;Xё!vs^sd:L*r.,XKK_s5Z$%Tfgg%ӌKb-B۽M^'i̤p#] +[J&1{%Gv@\,C.jh{kbJ8(0,n*^q͕e_t VWArԁ˴,Hآpѐ)y=eglDGUW޺6ܫbw(%!p&RBNVq pppp"Ҡh NXi0M =#amwι7sv1[f|ٿmz~y8Ja-W*lz`ؕ8jqV}j "'PVrL^S.E.v5AQ) AaJ5ދ4N.U=]#3jmii[T\¿ 17:h. (K@?Bc9P9bY+ig u/7n! ҾUع5Yb7&ɠ0k0|IwȼѴJW1m3FD)9hosG wn| (`tuXNa n@TEN VzL\#`٩Qx&O9) 9&߄jJ粬6{Q(<]#3jmii[K^(#=((W12֖ex!KTKwN'PEQEQI=Ff /d)((z̨n^REQEQE'QkKL2(((O12֖ex!KQEQEQUcdF- p 0hnkOj 0`4EQEQEQV12ֶ|X|E\Z8Yu !4B(((>ȌZ[`ZরB!Bz̨6e n l(((z̨6e n ^REQEQE'QkKlPB(((O12֖ؠ5)x!KQEQEQUcdF- A-k pSB(((>ȌZ[`Z,EQEQEQT}R4!4M Y((#3jmi jYChEQEQEQI=FfԲ7/d)((z̨6e n ^REQEQE'QkKlPB(((O12֖ؠ5)x!KQEQEQUcdF- A-k pSB(((>ȌZ[`Z,EQEQEQT}R4!4M Y((#3jmi jYChEQEQEQI=FfԲ7/d)((z̨6e n ^REQEQE'QkKlPB(((O12֖ؠ5)x!KQEQEQUcdF- A-k pSB(((>ȌZ[`Z,EQEQEQT}R4!4M Y((#3jmi jYChEQEQEQI=FfԲ7/d)(W+ |c]yz_?qB9XUQeVeNW9;#ꁚs5Ohw0.Dkko<EQz̨6e n ^REQvιeܪp1{ RU\gPUd5)cdF- A-k pSB(1{v|<{-恰uD020sfFwwhbyqPݚϟÌ6<)v %9h*@̻5M>,u\7H#'M=s mylp G^[1Ik|(*M12֖ؠ5)x!KQEܚg#fXLT& .[ٝw[oLdj46h %88yac UduYJ8hk{Qע@Q?|=IPݸhvH)J$QkKlPB(B=ε:_zV*0lrX,(1dE'c'/35t<}oS0S5c1cv+pge`kQ {!kec1clŜ0noYc167F1-L[1c1Ɔ͍QiKe1cascsiec1clŜ`Y"5iec1clŜdx/c1c+v3Vy \e1cascs5x2c1ذ19m Yjec1clŜ,x 5޲1c16lnbN[x\U߿?دoloYc167F1~ѽAYL+m h!4޲1c16lnbN[xoYc167F1-<^C,c1c ӖEf%gN,>_%)WrN4U2ՙD8pZ8qs`l,6-@_ HFWm,!`r56'-\[=:SO85pp[ #NZ^Q){A9m  Ӗf\DGJ#yG&` `guv&kjon7;'eaKVӖTkpo"`r6--\Y,'TpjiدPi8_QuF85D÷F8m  ӖUw6pԯ :tl˴#S0v+` w}0lPN[,>MN < |_nv,{6 ?,Zd7ׯDޫ@%`r~#GtAW?,0Ӷӟ[- y~}Nڑ#Go1cь{?,Zԯ8 `m360^BqFK4pԯ(3h`-c&`fo;!K-cf]XDS+y 8mqV+K}nߞ?+Y `ؠe|8 `ʜe|8OJpp1ଁi&`m36:=5ijH9{~XJ-c>;őO)N om.޽{o[}n۶g_}[/被ޛ8mqVnv _!Mv}ȑ'N^{^շ:X=u} 9mqnN5p|M7=Swq?N;-*A rږ1c q"]'ɛ9xjD/Fs|;mN! m36y$~KHٗ^zi׮]wy~ .୷ҷOgOuSO;v+ؾ}snrĉg}v:vϞ==X:0`pږ1c,q|h"hcpǀL;tMsΫoS.vV<ۧ?_]oo?_gB&-i[njMJNq֔E(~%կE"eEo~?P5; 8^xAtĉ[neǎ?޵_qN <yPl,SKmݦ7YNH:߾⋯_K[lQ|DJ3:E}ݓ,!Dڵ륗^jԬn?[Ӷ:8>O?aY'3 ޻w/6jVYIuYrȑ;v-cf~F#NZ5U For"e#@ݻ `}n߾}>O3-cf]X9YS _E&guw?ۨYM+ `ql׮]+رc3-"ʶ߾߀.E6>,ywχZM'+}o m36y;;3ZjIO< N8q]wm۶M|-i[njMy}y~P,qGXpj`>u/~Ç/l߾.:~-c&8JٙqVkjN o e˗\rɩm۶~zo?8mI"T{~۷7`-O")T>De|^ɏ0 N2>flNZ7~qf?&`8m36}߀n ॽ^b1cύQi[njzpjY'7~1c1V>7F1m36QڬEkϋX `i4#l~Ͽ<i[njw6tpiKwu-cƦ]nMTyGJ_9Ew- `j4pO˴e|ؔ ?,0lPN2>flNNK"7ipW[-cƦ]Έ$45Qv7E `cf4m36 /Jik-+\)vqږ1cSgbMV'%Ξ4>'pE`(-cƦJ$1A9mߞo,y} :X"89mq֢=WV'p_ 8mqVo[ ༁{֙ӶoXo5<HI<|#SGw5pBe|ظ}+QI\˿ׯ,_^&Sm36n?KTj+z3N:2"p;K. 8mq￟ i[njwXp `⾳.cSsږ1c]<`SȜN?`"pn`>f7_lzpϹ++0`M6Og <`NGz藝< @iW"}ɛQ5AFw:,n7p;_`#h#;78R]ZipĬD.4%NX ] `j`NvWN0)"e@kN `N< hը_s~ilIFG/{دox>_/ηT_>m</vcWs7.$[[/o_Gozv?6fesՍ \v7⛂ޢԧ͸+̱9xټW W>wg{_7w_%eq/yX<۹ _AzLzx\L{u0%9Rj^j9DddJe0HUYNٟyO`Qn<=F?_hI~w3N߂bl7ы8Wh?z7\퟽k-}ooo2+YZYol&Yϯ_!;9p]W:&NS.jدoT*+Y{~s3nس[qS+Qtʬ?V*  c=2?V*FUpXm9fc<\7p(*N<0lU?S^YR]%_iIen*'aO`ni $?@p'}Ȅn 0`' WNyO.ν+ׂ ,ߊ9UX%^~Fg^!발d֑֓qT4A'鯧 +.wܘ?:?=d ~AwMqV*QWC8OuOS7`ͯo&e~u-wqW$늮8FؔZ-Iy)oXWtսկhN ՙM3Bonph| zNQ~%55D*cWXn]>|m,eI4[)goݫ~,zT?\rدm.O p0SgJԯN[_qV& 18N+`qfsX|E `R`N?.]`%NX⩤n7pi @Iܨ_q_W]^/,>܋}_`#h#;Eks.pj`_1k,-c[۷[qoԯLXŏֺÿjpI 8mWܾkp51XsR/0,i[njMg=CLCԯ~eH"m36eaWR$~9n (-cU(mկD&7ŏu/7_ӶoMj_XgC +)S8_ͯPi[njM^)nJ~[++NqNݛ.Wׯ(-cf@GR}+iKx~ ]\~}N2>flUlFxFF 6;Ç'X'MRK<.7_Ӷ~Zipk.vHKoO+Se|DJ_(֨\Tm^`4EI `gXye|8̯߅,~:?wnدPi[njM˿]iKn~E`>@m36sxaJtD& (-cfҨ(\l_ `)0I"p~}N2>fl~Yo_iD} ϣ2 `i[nj?KgJl~[qQ~xx*Yϻe|ج$onJoKgij 8o~}N2>fl֯D^/$u@3#ţxzBfl `k[|w&eN55paK~}N2>fl֯D*Wݮ=+n߮˿=|"4Dc=n N (-c&WܢkVܾY4W `=|;&`8mUfF6E}+a>Mq+4_ӶU_q_I>7p "`)N2>flYϊcu~`fX=v4_Ӷ˿ϊԱ,>eE} e|8yg9y[0,i[njM#Uтl]ꭹ}+8]<uq򶸀+~}N2>flŦtWܾ>YHѽwK2e|ظ}(Ш}nuVc=3g-NY_-c] Q .ز?/+'o  rږ1cӨ_ Q(Vkه~XqxxQ_m!`)N>V?cIsѪ׊o_`ccdzg~}Nۊ{wc&3z33DR?}+ XsJ,N',>@m[536+Sj[p["%,G# 8m3nVڠ2u֖'xb^KTe۷ 8mgu֯ƌޔ6e3+ޚ۷'|C]RC=Sߚw÷ׇY޽{o gٹsc}[o]pW_}^H)U-cƑYlp"}%7qV3u?* sm߯*u^{饗?~77߬o߾{o]?^% ٵk׽ޫ ``8mqd.Wg÷<3,:k=v<`qxǎ_mݦ٣ >ӟ~iߣ߻o_R)Kki[njM4D6D:MWo%կģBEg/Ƿ'N8zYgO~^ KYX#N2>flԯHk⎭9|knߊ۷rGs#c8P4[n3o|[oO}Twq?OݞN>{p qO|/nxݻw?;Qzzo|N;S?Ϻ1^cA+\wunC^Ts4ZtfFD1c3~ъwoe&',O?wP;Մ{{ۧ?+"_Wko\xjZ_ ݫr6ms=ѣ΃رC o}[G'73_z]vu<|3ԧ>uE?~\V*Wy禇׿o)W_ՓK}|%U=eUa[njM%ъ۷|D&÷ `DH#[qP;qa6.*Mynԟ:J{!}}}Z gquGv#w}UW;X`=UJ5HOI/-XZW}se~Gxtm136YNWh[sV{C?M8K 8kތ_8]ݮ?}ѣGÊ2K_s:*?o}6R! _|qΝg3픍uˏ~/sύ' wyh|i[nj7z+N֚k=j?T<[q5*o]t5\kٳ'ٖpW^HxwuW'Bkz:PY8R+>K%W_gry8v!//O}N|?n l4Q|ظzkΚ÷XEƆ~Co۷}+ߚ_彗jirw}?ON;45gܸo>%hM`zw^QOyUW-`ÇLx&FZeƷ}Mt, R>fl57g[sV5o~|ǎfP:@IENDB`

Docs  /  NCRC Recurring Contracts  /  Working With The App  /  End Contract
 Working With Auto. Ending

Once a Contract line has been fully invoiced and is no longer to be extended, the status can be set to Ended via a Job queue entry, thus marking the Contract line as closed. A Contract line is set to the Ended status defined in the NCRC Recurring Contracts Setup when:
  • Status = Active/Cancelled
  • End Date > Work Date
  • Extension = Disabled
  • Payment Plan = Completly Billed

Docs  /  NCRC Recurring Contracts  /  Working With The App  /  Job Integration
 Job Setup

Activate Job integration to create Jobs for Contracts. Jobs for Contracts offer versatile advantages; for example, Customer and Vendor Contracts can be linked to calculate the actual profit of a Contract line.

Important

Jobs are also required to use Prepayments or to invoice at cost.
Open the NCRC Recurring Contracts Setup and enable Project Integration. In the Job No. for Contracts field, select the number series to be used when creating Jobs from Contracts & define a Default Job. Only after activating the Job Integration, the corresponding fields & actions will be displayed in the Contract. For more information, see Working With The App, Job Integration, Working With Job.

Docs  /  NCRC Recurring Contracts  /  Working With The App  /  Job Integration
 Working With Job

Use the Create Project action to create a project for a Contract. The project number is then entered in the corresponding field at the Contract header as well as the Contract lines.

Important

The lines must not be Active or Ended, otherwise the Job No. cannot be entered in the line.
Provided you have enabled Create Job Task and Planning Lines in the NCRC Recurring Contracts Setup, when enabled, a Job task and planning line will be created and assigned to the Contract line. The assignment of Job, Job Task & Job Planning Line can also be done manually. A Job is created for each Contract line. The Job Task No. is assigned based on the Start No. in the NCRC Recurring Contracts Setup. The description corresponds to the description of the Contract line. In addition, a Job Planning Line is created for each Contract line.
FieldValue
Planning DateStart date of the Contract line
Line TypeBudget
Document No.Contract No.
TypeContract line type
No.Contract line No.
DescriptionContract line description
QuantityTotal quantity for the complete duration of the Contract line
Unit CostCost price of the Contract line - if filled
Unit PriceSales price of the Contract line - if filled
Job Planning Lines that are linked to a Contract cannot be changed or posted or invoiced from within the Job. Please use the corresponding functions in the Contract. As soon as a Contract linked to a Job creates a sales invoice, a billable Job Planning Line is created, and it is invoiced. This creates a Job item of type sales on the Job, and the actual values end up on the Job. For more information, see Working With The App, Job Integration, Working With Job And Contract.

Docs  /  NCRC Recurring Contracts  /  Working With The App  /  Job Integration
 Working With Job And Contract

You can connect a Customer Contract and a Vendor Contract using a Job, thereby comparing the actual values from the purchase invoices and sales invoices. To do this, first create the Customer Contract and create a Job. Then create a Vendor Contract and select the Job number of the previously created Customer Contract. If there is a 1:1 mapping between Customer Contract line and Vendor Contract line; select the Job Task No. of the Customer Contract line. The Job is then populated with the budget cost amount and the actual costs from the Vendor Contract and the budget sales amount and the invoiced value from the Customer Contract.

Docs  /  NCRC Recurring Contracts  /  Working With The App  /  Prepayment
 Prepayment Setup

To manage Prepayment, you must enable Job Integration in the NCRC Recurring Contracts Setup. Also define the Prepayment Job Journal Name, the Prepayment Job Journal Batch Name and the Prepayment Journal Document No. to be used for posting Prepayments. For more information, see Working With The App, Prepayment, Working With Prepayment.

Docs  /  NCRC Recurring Contracts  /  Working With The App  /  Prepayment
 Working With Prepayment

Enter Prepayment line

Prepayments are fixed defined amounts/quantities which you charge your Customer in full and from which they can then call. To enter a new Prepayment, create a new Contract line and enter the No. as well as the quantity and price. Since a Prepayment is invoiced once and not continuously, the billing type must be removed in Prepayment lines. A Contract line of the Prepayment type therefore also has no Payment Plan. Check the Prepayment box and define the Prepayment type.
Prepayment TypeDescription
QuantityIt is called from a defined quantity, regardless of the amount that is consumed
AmountIt is called off from a defined amount, regardless of the actual amount called off
You can also define whether Business Central allows overbooking of the defined quantity or amount by enabling or disabling Overbooking Not Allowed. Before you can activate a Contract with a contingency line, you must link the Contract or Contract line to a Job.

Invoicing Prepayments

Prepayment invoices are usually issued at the beginning of the Contract. To create a Prepayment invoice, select the desired Contract line. Click on Line > Prepayment > Invoice Prepayment. An unposted invoice will be created which you can access and post via Line > Prepayment > Sales Invoice/Credit Memos.... In the Prepayment area in the info box, you can see if and what has been invoiced from your Prepayment.

Retrieve Prepayment in Contract

The actual consumed values can be entered either manually, or via Excel import. To enter the consumptions manually, select the desired Contract line and click Line > Prepayments > Use Prepayment. Then enter the consumption date and the quantity or value consumed. In the Prepayment area in the info box, you can see the retrieved values. If you have activated Overbooking not Allowed, the system checks that the quantity to be called off does not exceed the remaining quantity and issues an error message if necessary.

Retrieve Prepayment via Excel import

To be able to enter consumptions via Excel, you must create the associated data exchange definition. To do this, run the associated Create Default Data Exchange Definition action for Prepayments in the NCRC Recurring Contracts setup. A data exchange definition is then created in which it is defined how the Excel file must be structured for the import. Based on the default setup, the import file must be structured as follows:
Contract IDDescription 2Quantity
C.23-000019_10000additional description1
The Contract ID consists of Contract number_line numberadditional import-specific descriptionquantity retrieved
Seperator: Semicolon Headline: Yes Invoke the Import Contract lines from Data Exchange Definition function. Select the data exchange definition CONTRACT COST (= default data exchange definition) Select the posting type Consumption Based. Select the posting date for the line items. Activate reverse signs to create negative items. This can be used to reverse items that have already been imported and posted. Click OK and import the .csv file.

Docs  /  NCRC Recurring Contracts  /  Working With The App  /  Consumption Based
 Consumption Based Setup

To be able to invoice at cost, you must activate Job Integration in the NCRC Recurring Contracts Setup. Also, define the Default Job Journal and the Job Journal Name to be used for posting the expenses. Activate Automatically Get Consumptions if you want recorded expenses to be transferred directly to the Payment Plan. For more information, see Working With The App, Consumption Based, Working With Consumption Based.

Docs  /  NCRC Recurring Contracts  /  Working With The App  /  Consumption Based
 Working With Consumption Based

Activate Contract line for Consumption Based

Create a new Contract line, leaving the quantity blank, and enable Consumption Based. Before you can activate a Contract with a Contract line that is billed at cost, you must link the Contract or Contract line to a Job. In the created Payment Plan, the quantity and the line amount are then initially 0.00 in all periods.

Get Costs in the Contract

The actual consumed values can be entered either manually, or via Excel import. To enter the consumptions manually, select the desired Contract line and click Line > Consumption > Add Consumptions. Then enter the Posting Date and the Quantity To Transfer To Journal.

Get Costs via Excel import

To be able to enter consumptions via Excel, you must create the associated data exchange definition. To do this, run the associated Create Default Data Exchange Definition for Consumption Based action in the NCRC Recurring Contracts Setup. A data exchange definition is then created in which it is defined how the Excel file must be structured for the import. Based on the default setup, the import file must be structured as follows:
Contract IDDescription 2Quantity
C.23-000019_10000additional description1
The Contract ID consists of Contract number_line numberadditional import-specific descriptionquantity retrieved
Seperator: Semicolon Headline: Yes Invoke the Import Contract lines from Data Exchange Definition function. Select the data exchange definition CONTRACT COST (= default data exchange definition) Select the posting type Consumption Based. Select the posting date for the line items. Activate reverse signs to create negative items. This can be used to reverse items that have already been imported and posted. Click OK and import the .csv file.

Docs  /  NCRC Recurring Contracts  /  Working With The App  /  Scheduled Change
 Scheduled Change Setup

To use Scheduled Changes, you must enable them in the NCRC Recurring Contracts Setup. By activating it, two new Contract line actions will be displayed. This allows Scheduled Changes to be created for past and future periods. Scheduled Changes can only be made at the Contract line level, not at the Contract header level, and may result in sales invoices or sales credit memos, if applicable. If you activate Scheduled Changes, you can only make changes using the associated functions. If you try to change the quantity, the price or the start and end date of the line, an error message will be displayed.

Caution

Scheduled changes cannot be executed for Contract lines of type Prepayment or Consumption Based.
When a scheduled change is executed, the status is briefly set to the defined change status and the change entered via the input mask is executed. This means that changes that have been made can also be tracked retrospectively via the Status Change Log.

Important

Documents which are created by scheduled changes must be posted and cannot be cancelled. If you want to cancel a document created from a scheduled change or undo the change, you must make an additional scheduled change.

Docs  /  NCRC Recurring Contracts  /  Working With The App  /  Scheduled Change
 Working With Qty. Increase

An increase in quantity, for a period already invoiced, results in a sales invoice for one or more periods.

Example:

Initial situation: Quantity in the Contract line: 2 Price in the Contract line: 100,00 Start date: 01.01.23 End date: 31.12.23 Billed Until: 31.03.23 Input: New Quantity: 3 – the quantity is increased from 2 to 3 New Unit Price: 0,00 – the Unit Cost in the Contract line doesn’t change Date for Change: 01.02.23 – the period from which the change comes into force Posting Date: 01.02.23 – the posting date of the sales invoice Status for Change: the status that is set briefly to execute the change Combine Periods: If activated, sales invoices which concern several periods are summarized on one invoice. Change Dimensions: see Working With The App, Dimensions, Dimensions in Contract Result: However, the quantity was increased from 2 to 3 in period 2, which leads to an increase in the line amount and thus triggers a sales invoice. The sales invoice is created but not posted and can be seen in the relevant Payment Plan lines in the additional table No. of Related Documents. Click on the number to open all the documents that are assigned to the Payment Plan line. You can also see by which function the document was created. Click Source Document to open and post the sales invoice. The quantity in the Contract line has also been increased as the new quantity affects the next billing interval.

Docs  /  NCRC Recurring Contracts  /  Working With The App  /  Scheduled Change
 Working With Price Increase

An increase in the price, for a period already invoiced, results in a sales invoice for one or more periods.

Example:

Initial situation: Quantity in the Contract line: 3 Price in the Contract line: 100,00 Start date: 01.01.23 End date: 31.12.23 Billed Until: 31.03.23 Input: New Quantity: 0 – the quantity remains the same New Unit Price: 200,00 – the Unit Cost in the Contract line increases from 100,00€ to 200,00€ Date for Change: 01.02.23 – the period from which the change comes into force Posting Date: 01.02.23 – the posting date of the sales invoice Status for Change: the status that is set briefly to execute the change Combine Periods: If activated, sales invoices which concern several periods are summarized on one invoice. Change Dimensions: see Working With The App, Dimensions, Dimensions in Contract Result: The unit price has been increased from 100 to 200 in period 2, which results in an increase in the line amount and thus triggers a sales invoice. The sales invoice is created but not posted and is visible in the relevant Payment Plan lines in the additional table No. of Related Documents and can be posted. The Unit Price in the Contract line has also been increased as the new price affects the next billing interval.

Docs  /  NCRC Recurring Contracts  /  Working With The App  /  Scheduled Change
 Working With Qty. Decrease

A decrease in quantity, for a period already invoiced, results in a sales credit to one or more periods.

Example:

Initial situation: Quantity in the Contract line: 3 Price in the Contract line: 200,00 Start date: 01.01.23 End date: 31.12.23 Billed Until: 31.03.23 Input: New Quantity: 2 – the quantity is reduced from 3 to 2 New Unit Price: 0,00 – the Unit Cost remains the same Date for Change: 01.02.23 – the period from which the change comes into force Posting Date: 01.02.23 – the posting date of the sales invoice Status for Change: the status that is set briefly to execute the change Combine Periods: If activated, sales invoices which concern several periods are summarized on one invoice. Change Dimensions: see Working With The App, Dimensions, Dimensions in Contract Result: However, the quantity has been reduced from 2 to 1 in period 2, which results in a reduction of the line amount and thus triggers a sales credit memo. The sales credit memo is created but not posted and is visible in the relevant Payment Plan lines in the additional table No. of Related Documents and can be posted there. The quantity in the Contract line has also been increased as the new quantity affects the next billing interval.

Docs  /  NCRC Recurring Contracts  /  Working With The App  /  Scheduled Change
 Working With Price Decrease

A decrease in the price, for a period already invoiced, results in a sales credit memo to one or more periods.

Example:

Initial situation: Quantity in the Contract line: 2 Price in the Contract line: 200,00 Start date: 01.01.23 End date: 31.12.23 Billed Until: 31.03.23 Input: New Quantity: 0 – the quantity remains the same New Unit Price: 100,00 – the unit cost decreases from 200 to 100 Date for Change: 01.02.23 – the period from which the change comes into force Posting Date: 01.02.23 – the posting date of the sales invoice Status for Change: the status that is set briefly to execute the change Combine Periods: If activated, sales invoices which concern several periods are summarized on one invoice. Change Dimensions: see Working With The App, Dimensions, Dimensions in Contract

Caution

For scheduled changes in periods that have already been billed, a posting date must be specified, otherwise the resulting document cannot be posted.
Result: However, the unit price has been reduced from 200 to 100 in period 2, which results in a reduction of the line amount and thus triggers a sales credit memo. The sales credit memo is created but not posted and can be seen in the relevant Payment Plan lines in the additional table Number of Assigned Documents and can be posted there. The unit price in the Contract line has also been increased as the new price affects the next billing interval.

Docs  /  NCRC Recurring Contracts  /  Working With The App  /  Scheduled Change
 Working With Qty. Change in Future Periods

A change does not result in the creation of documents it only adjusts the payment schedule.

Example:

Initial situation: Quantity in the Contract line: 2 Price in the Contract line: 100,00 Start date: 01.01.23 End date: 31.12.23 Billed Until: 31.03.23 Input: New Quantity: 3 – the Quantity increases from 2 to 3 New Unit Price: 0,00 – the Unit Price remains the same Date for Change: 01.05.23 – the period from which the change comes into force Posting Date: can be left blank as this entry does not trigger a sales document Status for Change: the status that is set briefly to execute the change Combine Periods: If activated, sales invoices which concern several periods are summarized on one invoice. Change Dimensions: see Working With The App, Dimensions, Dimensions in Contract Result: The quantity has been increased from 1 to 2 starting from period 5, which results in an increase of the line amount but no additional document. The quantity in the Contract line has not been increased because the new quantity does not yet affect the next billing interval. Only when the new quantity affects the next billing interval, the new quantity is automatically transferred to the Contract line.

Docs  /  NCRC Recurring Contracts  /  Working With The App  /  Scheduled Change
 Working With Price Change in Future Periods

A change does not result in the creation of documents it only adjusts the payment schedule.

Example:

Initial situation: Quantity in the Contract line: 1 Price in the Contract line: 100,00 Start date: 01.01.23 End date: 31.12.23 Billed Until: 31.03.23 Input: New Quantity: 0 – the Quantity remains the same New Unit Price: 50,00 – the Unit Price is decreased to 50,00 Date for Change: 01.05.23 – the period from which the change comes into force Posting Date: can be left blank as this entry does not trigger a sales document Status for Change: the status that is set briefly to execute the change Combine Periods: If activated, sales invoices which concern several periods are summarized on one invoice. Change Dimensions: see Working With The App, Dimensions, Dimensions in Contract Result: The unit price has been reduced from 100 to 50 starting from period 5, resulting in a reduction of the line amount but no additional document. The unit price in the Contract line has not been changed, because the new price does not affect the next billing interval yet. Only when the price affects the next billing interval, it will be automatically transferred to the Contract line.

Docs  /  NCRC Recurring Contracts  /  Working With The App  /  Scheduled Change
 Working With Date Change

There is the possibility to change the start and end date of a Contract line afterwards. To do this, open Functions > Scheduled Date Changes on the Contract line. You can then enter a new start or end date. If you set the start date later and the first period has already been invoiced, a sales credit note will be created for it. However, the original first period is no longer included in the new Payment Plan, and can therefore only be accessed and posted via the previous version of the Payment Plan.

Docs  /  NCRC Recurring Contracts  /  Working With The App  /  Bundles
 Working With Bundles

To use Bundles, you must enable them in the NCRC Recurring Contracts Setup. This will cause two new fields to appear in the Contract lines as well as sales invoice lines:
  • Bundle
  • Belongs To Bundle
  • Print Line
  • Print Quantity
  • Print Price
In the Bundle field, select the Bundle value to enter the Bundle creation screen and create your Bundle there. Bundles consist of a text line as a header and one or more item lines and are created for each Contract. You can create the Bundle description as a default text and select it in the No. field, the components will be added individually. Certain values, such as the term and extension and termination type, are maintained at the Bundle header level and automatically copied to all component lines. By clicking OK, the Bundle will be added to the Contract. The Bundle line (=Bundle header) is a remark line and is displayed in bold, the component lines are assigned to the Bundle header line via the respective line ID in the Belongs to Bundle field. By default, the text, the quantity and the price are printed for the Bundle line. Printing is disabled for the component lines, but can be enabled for each individual component.

Important

The print logic can only be used in conjunction with RDLC documents that have implemented this logic.
The quantities and prices of the component lines are taken from the Bundle entry. The Bundle line receives the value 1 by default, the line amount corresponds to the sum of the line amounts of the associated components. If the quantity in the Bundle is changed, the Bundle's unit price is automatically adjusted so that the line amount per billing interval continues to equal the sum of the components. Values which must remain the same for the entire Bundle (e.g. Billing Type, Cancellation Type, etc.) cannot be changed in the Contract line. If these values must be edited afterwards, the Bundle entry mask can be called via Functions > Open Bundle. All components of a Bundle must always have the same status. If you change the Contract line status of a component line, the status of all component line is automatically changed. Payment Plans are created for the respective component lines, just as for normal Contract lines, and can then also be transferred to a sales invoice. The print options from the Contract line are transferred to the invoice.

Docs  /  NCRC Recurring Contracts  /  Setup
 NCRC Recurring Contracts Setup

Here you can specify the general settings and defaults for the NCRC Recurring Contracts.

General, Fields

Default StatusSpecifies the default status used when creating the contract.
Active StatusSpecifies the active status used to set a contract to a billable status.
Cancellation StatusSpecifies the Cancellation status used for the Cancellation.
Extension StatusSpecifies the Extension status used for the Cancellation.
Ending StatusSpecifies the Ending status used for the Ending of a contract.
Set Day of Period Start to Starting DateSpecifies by default whether the day of the period start should be automatically adjusted to the start date for Contract lines with different start date.
Default Day of Period StartSpecifies the default value of the Day of Period Start.
Default Reason CodeSpecifies the default value of the Reason Code.
Contract Dimension CodeSpecifies the contract dimension code. When a new Contract is created, a new dimension value consisting of Contract No. and Contract Description is automatically created.
TODO_"Autom. Approval Request at Invoicecreation"Specifies that the approval request is created automatically if sales invoice approval is enabled.
TODO_"Limit Amount for Contract Invoice"Specifies the minimum value that a sales invoice created from a Contract must show. Invoices below this amount are not generated and the period is marked as invoiced.
Default Source TypeSpecifies the default value of the Source Type.
Print Only Period On InvoiceSpecifies whether the remark line in the sales invoice contains only information about the period (excl. Contract data).
Enable BundlesSpecifies whether the bundle functionality has been enabled.
Line Text For BundlesSpecifies whether only one remark line should be printed for a Bundle or one remark line per component.

Numbering, Fields

TODO_"Contract Nos"Specifies the code of the number series used to assign numbers to Contracts.
Contract Invoice Nos.Specifies the code of the number series used to assign numbers to Contract Invoices.
TODO_"Contract Cr.Memo Nos."Specifies the code of the number series used to assign numbers to Contract Cr. Memos.
Posted Contract Invoice NosSpecifies the code of the number series used to assign numbers to Posted Contract Invoices.
Posted Contract Cr. Memo Nos.Specifies the code of the number series used to assign numbers to Posted Contract Cr. Memos.

Dimensions, Fields

Enable Shorcut Dimension 3Specifies whether the shortcut dimension code 3 should be displayed.
Enable Shorcut Dimension 4Specifies whether the shortcut dimension code 4 should be displayed.
Enable Shorcut Dimension 5Specifies whether the shortcut dimension code 5 should be displayed.
Enable Shorcut Dimension 6Specifies whether the shortcut dimension code 6 should be displayed.
Enable Shorcut Dimension 7Specifies whether the shortcut dimension code 7 should be displayed.
Enable Shorcut Dimension 8Specifies whether the shortcut dimension code 8 should be displayed.

Role Center, Fields

Date Fromula for expiring ContractsSpecifies the Date Formula for the Cue No. of expiring Contract Lines.

Scheduled Changes, Fields

Disable Manual Changes on Contract LineSpecifies whether manual changes to the contract line have been deactivated. Changes can then only be made via the scheduled change functionality.
Retrospective IndexingSpecifies whether past periods are also taken into account during indexing. A difference invoice/cr. memo is then created for periods that have already been invoiced.
Change StatusSpecifies the change status that will be set for the scheduled changes.

Indexing, Fields

Indexing StatusSpecifies the Indexing status used for the Indexing.
Indexing Unit Cost RoundingSpecifies the rounding of the unit code field after an indexing
Indexing Unit Price RoundingSpecifies the rounding of the unit price field after an indexing

Job (Prepayment/Consupmtion), Fields

Enable Job IntegrationSpecifies whether job integration has been activated. Integration must be activated to record Prepayments/consumption.
Default JobSpecifies the Job number that will be used as a template from the Contract, when Create Job is executed.
Job Nos. for ContractsSpecifies the code of the number series used to assign numbers to Jobs from Contracts.
Create Job Task and Planning LinesSpecifies whether to automatically create the job tasks and planning lines for the contract lines.
Job Task No. Start No.Specifies the start number of the Job tasks and is always incremented by 1.

Prepayment, Fields

Prepayment Job Jnl. Document Nos.Specifies the Job journal document number used to post when getting Prepayment.
Prepayment Job Jnl. NameSpecifies the Job journal template used to post when getting Prepayment.
Prepayment Job Jnl. Batch NameSpecifies the Job journal batch name used to post when getting Prepayment.

Consumption, Fields

Consumption Job Jnl. NameSpecifies the Job journal template used to post consumption.
TODO_"Consumption Job Jnl. Batch Name"Specifies the Job journal batch name used to post consumption.
Automatically Get ConsumptionsSpecifies whether entered or imported consumptions are automatically transferred to the Payment Plan.

Sales, Fields

Sales Release Needed at Contract CreationSpecifies whether a sales quote or sales order must be in Released status for a contract to be created.

Purchase, Fields

TODO_"Gen. Journal Document Nos. Purchase Invoice"Specifies the Gen. Journal Document Nos. Purchase Invoice used to post an purchase invoice.
TODO_"Gen. Journal Template Purchase Invoice"Specifies the value of the Gen. Journal Template Purchase Invoice field.
TODO_"Gen. Journal Name Purchase Invoice"Specifies the value of the Gen. Journal Name Purchase Invoice field.
Purchase Release Needed at Contract CreationSpecifies whether a purchase quote or purchase order must be in Released status for a contract to be created.

Import, Fields

Contract Import Attribute IDSpecifies the Contract Import Attribute ID for the import.
Contract Import AttributeSpecifies the Contract Import Attribute for the import.

Reminder, Fields

ActiveSpecifies whether the reminder is active for contracts that are about to expire.
PeriodSpecifies the period from which a reminder should be sent out for a Contract. 1M = A reminder will be sent starting 1 month before the end date
RecipientSpecifies the recipient of the reminder.
E-MailSpecifies wheter the reminder will be send via E-Mail.
TeamsSpecifies wheter the reminder will be send via Teams.
E-Mail SubjectSpecifies the subject of the reminder E-Mail.
E-Mail-Notification TextSpecifies the content of the E-Mail
Flow URLSpecifies the request URL of the Power Automate Flows.

Actions

  • Create Default Data Exchange Definition for Consumption Based

    Executes the Create Default Data Exchange Definition for Consumption Based action.
  • Create Default Data Exchange Definition for Prepayment

    Executes the Create Default Data Exchange Definition for Prepayment action.
  • NAVAX License Management

    Opens the NAVAX License Management which displays the current license status of the NAVAX extensions.

Docs  /  NCRC Recurring Contracts  /  Appendix
 NAVAX License Management

The NAVAX License Management page (in older versions "NAVAX License Overview" or "NCEX License Overview") displays the current license status of the NAVAX extensions.

Fields

NameSpecifies the name of the Extension.
License StatusSpecifies the current license status of the Extension.
Serial No.Specifies the serial number of the Extension.
VersionSpecifies the currently installed version of the Extension.

Trial Version

A NAVAX extension can be tested or used free of charge for 30 days after installation. After that, the extension can only be used with a valid license.

Request License

The license can be requested or checked via the Current Status action. This opens a window. The following example shows the NAVAX extension Excel Report Builder. Fill in the fields in the window and then click Send License Request. Please note that the licensing process may take some time. In the next few days you will receive an email with further information.

Note

For licensing, calling the online help and performing some actions, access to https://www.navax.app must be granted.

Public IP from www.navax.app for setting firewall access:
94.136.22.236, Port: TCP/443

Checking the connection to https://www.navax.app using PS:
Test-NetConnection navax.app -port 443
(PS must be performed with the M-Tier service user)

CRL Servers
In addition, the following CRL Servers must also be accessible for the certificate check:
https://certificates.godaddy.com/*
http://crl.godaddy.com/*
or their IP: 192.124.249.36

Activate/Update License

As soon as the licensing has been completed, you will receive an email and the license can be activated via the Update License action. The license is company independent. So it does not matter in which company the action is called.

Note

  • The licence must be updated once a year via the Update License action.
  • The update is only possible or necessary within the last 30 days before the license expires, or afterwards. Within the last 30 days before the license expires, notes are displayed.
  • If the Automatic License Renewal is enabled, the Update License action is called automatically before the license expires. Note that the setting is only active after the license has been activated via the action.

Terms & Conditions

For more information, see https://www.navax.app/EULA.php?L=en

Data Security

For more information, see https://www.navax.app/privacyStatement.php?L=en

Submit Rating

This action can be used to open the Microsoft AppSource ratings page for the extension. We would be very happy if you submit your rating and let us know about your experience with the Extension.

Docs  /  NCRC Recurring Contracts  /  Appendix
 Installation Notes

Publish and Install the Extension


All necessary steps are described here:
[Microsoft Learn] Business Central - Publishing and Installing an Extension

Dependencies

  • NAVAX Extension Base

    ID: 2f4cb42d-6e2a-4708-a5e2-3ec5f32f20e9 For more information, see [Docs] NAVAX Extension Base - General
  • NCDT Document Text Base

    ID: 2f97a39f-60f1-45d1-8bb2-7497bee60684

On-Premises

The following Granules are required for an On-Premises installation:
  • 70714830 NCRC Recurring Contracts by NAVAX
  • 1010860 Extension Base by NAVAX
  • 70714775 NCDT Document Text by NAVAX

External Addresses

  • https://www.navax.app

    For licensing, calling the online help and performing some actions, access to https://www.navax.app must be granted.

    Public IP from www.navax.app for setting firewall access:
    94.136.22.236, Port: TCP/443

    Checking the connection to https://www.navax.app using PS:
    Test-NetConnection navax.app -port 443
    (PS must be performed with the M-Tier service user)

    CRL Servers
    In addition, the following CRL Servers must also be accessible for the certificate check:
    https://certificates.godaddy.com/*
    http://crl.godaddy.com/*
    or their IP: 192.124.249.36

Docs  /  NCRC Recurring Contracts  /  Appendix
 Release Notes

Would you like to know what has changed in the extension?
Below you'll find an overview of the new features and changes made in the updates.

Version 21.1.3.1

as of Business Central 21
2024/11/07
  • Modifications

    • The Amount per month field on the contract card in the Invoice details tab has been renamed to Amount per month and the calculation has been adjusted accordingly.
    • The page Contract PP Line Details is no longer editable.
  • Corrections

    • You can now change the Bundle Quantity for the following documents after copying them:
      • Sales Invoice
      • Sales Credit Memo
      • Posted Sales Invoice
      • Posted Sales Credit Memo
      If you change the Bundle Quantity, the unit price is recalculated.

Version 21.1.3.0

as of Business Central 21
2024/10/29
  • Improvements

    • It is possible to add a comment to scheduled changes.
    • The Contract Change Log is extended by following fields:
      • Quantity
      • Unit Price
      • Starting Date
      • Ending Date
      • Extension
    • The Request Page for scheduled changes got extended by following fields:
      • Initial Quantity
      • Initial Unit Price
    • The Request Page for scheduled date-changes got extended by following fields:
      • Initial Starting Date
      • Initial Ending Date
  • Corrections

    • When creating projects with foreign currency from the contract, the currency code is now transferred correctly.
    • The error message when changing the start date of an active contract line has been adjusted.

Version 21.1.2.2

as of Business Central 21
2024/06/27
  • Corrections

    • When using bundles in contract lines, the description from the bundle lines is transferred to the contract line.
    • The combine periods option in the Create contract sales invoice action in connection with various one-time-payments on the contract now behaves correctly.
  • Modifications

    • The status of the contract is now set based on the status of the lines; the following rules apply:
      • Active: At least 1 line in the contract with "Active" status
      • Default: No line in the contract on "Active" and at least one line in the contract on "Standard status"
      • Cancellation: No line in the contract on "Active" or "Standard status" and at least one line in the contract on "Cancellation status"
      • Finished: No line in the contract on "Active", "Standard" or "Cancellation" and at least one line in the contract on "Finished status"
      • If the status of the lines cannot be clearly determined, the "Default" status is set

Version 21.1.2.1

as of Business Central 21
2024/05/29
  • Corrections

    • One-time payments do not have to be taken into account for automatic ending.

Version 21.1.2.0

as of Business Central 21
2024/05/27
  • Improvements

    • Contract line details for a better overview of entered values per contract line
    • One Time Payments in Contracts
    • New Functionality Release / Reset Status on the Contract Header
    • New Contract Period Multi-Annually
  • Modifications

    • Contract lines with a Sales/Purchase Order No. associated can be deleted, as long as no documents have been created.
    • Improved contract period checks when activating a contract line, entering a scheduled change or adding an extension period
    • Sales Orders can now be added to an existing contract with a different contact
  • Corrections

    • Rounding is deactivated as soon as a scheduled change has been made

Version 21.1.1.1

as of Business Central 21
2024/04/10
  • Modifications

    • Power BI Factboxes that are no longer supported have been replaced.

Version 21.1.1.0

as of Business Central 21
2023/10/27
  • Modifications

    • Changed the caption of Quota and Bill At Cost for language code EN to Prepayment and Consumption Based.
  • Corrections

    • When extending a contract line then payment plan was created incorretly.

Version 21.1.0.0

as of Business Central 21
2023/10/16
  • Initial Version

  Save manual as PDF or print  
DE|EN Imprint