KamoCRM

Raise and send a claim from the queue that found the work

Featurekamo-internal
已装运
2026年8月26日 21:55 UTC
作者
kamo
提交
336ebcb

The revenue cycle read seven queues and could not raise a claim. Each write now hangs off the queue that surfaced the need for it rather than living on a screen of its own. "Never charged" is a list of procedures performed with no charge and no stated reason — nothing failed and nothing told anybody — so the useful thing beside each row is creating the charge. The row leaves the queue once it exists, which is the point of the queue. Sending is offered only on a claim still in DRAFT. Re-sending an accepted claim is how a practice gets paid twice and then recouped, and the payer's duplicate logic is not something to rely on noticing. The confirmation says the claim is a draft and to check it before sending, because the two steps are deliberately separate and "raised" alone would leave people believing it had gone to the payer. Both actions are absent without MANAGE_CLAIMS. Refusals carry the server's own sentence, which names a self-pay restriction or a missing permission — either is more use than anything this screen could invent.

所有更改

就像你看到的运输?

所有东西都是靠自己运入你的工作空间的 从免费计划开始,一个月后再读这页.

永远开始自由查看定价