Since a charge such as labor can be of either two types (proposed or actual) that is a one-to-many relationship. Thinking about it further, it might be better to associate the charge type (labor, ODC, other) to whether it is proposed or actual in a table and then reference that in the contract charges table. This will replace the 2 fields in tblContractCharges with 1 field as shown below
tblChargeType (records for each: labor, ODC, other)
-pkChargeTypeID primary key autonumber
-txtChargeType
tblProposedorActual (you might have a better name, but this table would hold the two names: proposed and actual each as a record)
-pkProposedActualID primary key, autonumber
-txtProposedorActual
tblChargeTypeProposedorActual
-pkCTPAID primary key, autonumber
-fkChargeTypeID foreign key to tblChargeType
-fkProposedActualID foreign key to tblProposedorActual
tblContractCharges
-pkContractChargeID primary key, autonumber
-fkContractID foreign key to contract table
-fkCTPAID foreign key to tblChargeTypeProposalorActual
-ChargeAmt
Having records such as this: ProposedLabor, ProposedODC, ProposedTravel ActualLabor, Actual ODC and ActualTravel will make it harder to filter the data if you want to work with the charges from the groups separately.