nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Scheduled Payments

Sue Fulton

Is anyone else having trouble getting payments to move from contingent to scheduled? Our process is to create a payment requirement for each payment. However, in the last few weeks, after the requirement is fulfilled, the payment is not changing to scheduled. Thank you for any insight you can provide. Perhaps the process is different in SKY.

Find more posts tagged with

Comments

Sarah Hibler

Yes! I saw the same thing back in July. Support acknowledged a glitch. I abandoned using payment requirements because of it. My workaround is working OK for now: I created a requirement type at the request level to track the contingent condition (building permit, etc.). Then, I created a new code (Blueprint > Classification Tables) to tag the request itself as contingent. More clicks than it should be, but its working OK for us right now.

Louisa Robinson

Yes I've had this in sky - but i also had instances of this happening in classic (as it happened with someone who hadnt been added to Sky yet)

Its weird because with classic you have to tick to confirm the payment changing from contigent to scheduled - and I was told this was this bit that was missed & just closed down, so thats why it didnt change - BUT with Sky you should just get the confirmation tote appear now, theres no push to tick to confirmt this - so it should automatically happen.

As an admin of the system I have created myself a part to flag any of these as a warning, which I check regularly and make sure any that havent been changed is unmarked as done and marked as done again, but its a pain. The part is contigent payments with requirements marked as done:

(Payments.Status_ID = 160 and Payments.ID IN (select Payment_ID from Activities where Activities.Done_Flag = -1 and Activities.Class = 4) AND Payments.ID NOT IN (select Payment_ID from Activities where Activities.Done_Flag = 0 and Activities.Class = 4))

Sue Fulton

BB fixed the glitch on Friday, all seems to be working ok now.